Virtual ticket-in and ticket-out on a gaming machine

ABSTRACT

A gaming system compatible with patron-controlled portable electronic devices, such as smart phones or tablet computers, is described. The gaming system can include electronic gaming machines that are compatible to receive both virtual ticket vouchers and printed ticket vouchers that are redeemable for credits on the electronic gaming machines. Information associated with a virtual ticket voucher can be stored on a patron-controlled portable electronic device and then can be wireless transmitted to the electronic gaming machines. The electronic gaming machines can be configured to issue virtual ticket vouchers and printed ticket vouchers that can be redeemed for cash or additional game play on another electronic gaming machine. In one embodiment, the electronic gaming machine can be configured to issue a virtual ticket voucher to a patron-controlled portable electronic device.

BACKGROUND

1. Field of the Described Embodiments

The described embodiments relate generally to gaming systems, such asgaming systems deployed in a casino enterprise. More particularly,apparatus and method for moving value on and off of an electronic gamingmachine are described.

2. Description of the Related Art

An electronic gaming machine (EGM) that is configured to provide awager-based game can be likened to a combination of an automatic tellermachine and a home gaming console. The automatic teller machine aspectrelates to the cash handling capabilities of the EGM which allow it tosecurely receive, store and dispense cash or an indicia of creditredeemable for cash. The home gaming console aspect relates to the gamegeneration capabilities of the EGM, which allow it to generate anddisplay games that are entertaining to a user of the EGM.

To provide cash handling capabilities, a common configuration for anEGM, such as a video slot machine or mechanical slot machine, is toinclude a bill validator and a ticket printer. The bill validator isconfigured to accept and validate cash currency and ticket voucherswhere the ticket vouchers are bearer instruments redeemable for cash orgame play on an EGM. Accepted cash or ticket vouchers can be convertedto credits that are used to make wagers on the EGM. The accepted ticketsare stored within a cash box secured within a locked EGM cabinet. When aplayer wishes to leave and has credits remaining on the EGM, the creditsare converted to a cash value and are output as a ticket voucher via theprinter where the cash value is typically printed on the ticket. Theprinted ticket voucher can be used to add credits to another EGM or theprinted ticket voucher can be redeemed for its cash value.

Significant labor costs result from using a bill validator and a ticketprinter on an EGM. The labor costs involve periodically removing a cashbox including received tickets and cash from the EGM and replacing itwith an empty one, counting the cash and tickets removed from the EGMand refilling the ticket stacks on the EGM. Other cash handlingconfigurations also involve similar labor costs. For instance, EGMs caninclude coin acceptors and coin dispensers. The use of these devicesrequires periodically removing coins or adding coins to the EGM. Then,the coins retrieved from each EGM are counted on an EGM by EGM basis.

For security purposes, a technician and one or more security providersare typically involved in operations where cash is removed from an EGM.The security providers make sure the cash is retrieved and transportedwithout theft. Further, since removing cash requires the EGM cabinet tobe opened, the security providers observe the operation to make surethat tampering doesn't occur with the EGM hardware. An individual mightwish to tamper with an EGM to get it to award jackpots, receive cash ordispense cash in an unintended manner. The removed cash is transportedto a secure area where additional individuals are involved in countingand recording the various sums of cash and/or ticket vouchers removedfrom each EGM. The cash amounts removed from each EGM are reconciledwith other information sources, such as from hard meters on the EGM orrecords from a server that generates and validates ticket vouchers. Thereconciliation process is important for ensuring the earnings from theEGM are properly taxed.

Gaming enterprises operating electronic gaming machines are alwayslooking for ways of reducing labor costs. In view of the above, newmethods of cash handling are desired that reduce the labor costsassociated with operating EGMs.

SUMMARY OF THE DESCRIBED EMBODIMENTS

A gaming system compatible with patron-controlled portable electronicdevices, such as smart phones, netbooks, laptops, tablet computers,smart cards and memory sticks, is described. The gaming system caninclude gaming devices, such as electronic gaming machines and systemservers. The portable electronic devices can be configured to store andtransmit virtual ticket voucher information to an EGM or a redemptionkiosk and receive a virtual ticket voucher issued from the EGM. The EGMcan include one or more wireless interfaces and can be configured tocommunicate using one or more different wireless communicationprotocols. The wireless interface communication interfaces and wirelesscommunication protocol capabilities can enable communications with theportable electronic devices. In a particular embodiment, the EGM caninclude a wireless interface compatible with a near-field wirelesscommunication protocol.

In a particular embodiment, an EGM can be configured to redeem and issueboth virtual ticket vouchers and printed ticket vouchers. The virtualticket vouchers can be redeemed on other EGMs for credits used to placewagers on a game of chance generated or can be redeemed at a redemptionkiosk for cash. The virtual ticket vouchers can be stored on apatron-controlled portable electronic device. In one embodiment, thevirtual ticket vouchers can be compatible with existing cashless voucherhandling systems that provide for the issuance and redemption of printedticket vouchers. Thus, the cashless voucher handling system can beconfigured to provide for the validation, redemption and issuance ofboth printed ticket vouchers and virtual ticket vouchers.

One aspect of the embodiments described herein is related to anelectronic gaming machine (EGM). The EGM can be generally characterizedas including 1) a cabinet; 2) a display mounted to the cabinet; 3) awireless interface for communicating with a portable electronic device;4) a network interface for communicating with a validation serversecured within the cabinet; 5) a printer configured to print ticketvouchers communicatively coupled to a game controller secured within thecabinet; 6) a cash out button coupled to the game controller forgenerating a signal to transfer value from the EGM via a printed ticketvoucher and 7) a game controller including a processor and a memorysecured within the cabinet.

The game controller can be configured to 1) control a wager-based gameplayed on the electronic gaming machine; 2) issue virtual ticket voucherand printed ticket vouchers, 3) receive an indication, separate from thecash out button signal, to transfer value from the EGM via a virtualticket voucher, receive a validation number from the validation servervia the network interface, generate a virtual ticket voucher includingthe validation number, issue the virtual ticket voucher by transmittingthe virtual ticket voucher to the portable electronic device via thewireless interface; and 4) cancel the virtual ticket voucher transactioninitiated in response to receiving the indication to transfer value fromthe EGM via the virtual ticket voucher and issue a printed ticketvoucher including the validation number by instructing the printer togenerate the printed ticket voucher.

Another aspect of the embodiments described herein can also be relatedto an EGM. The EGM can be generally characterized as including 1) acabinet; 2) a display mounted to the cabinet; 3) a wireless interfacefor communicating with a portable electronic device; 4) a networkinterface for communicating with a validation server secured within thecabinet; 5) a bill validator coupled to the game controller configuredto accept bills and printed ticket vouchers, 6) a removable cash boxcoupled to the bill validator for receiving accepted bills and printedticket vouchers and 7) a game controller including a processor and amemory secured within the cabinet.

The game controller can be configured to 1) control a wager-based gameplayed on the electronic gaming machine; 2) redeem virtual ticketvouchers and printed ticket vouchers, 3) receive an indication totransfer value to the EGM via a virtual ticket voucher, receive thevirtual ticket voucher including a virtual ticket voucher validationnumber from the portable electronic device via the wireless interface,4) validate the virtual ticket voucher with the validation server viathe network interface, 5) deposit a credit amount associated with thevirtual ticket voucher and 6) notify the validation server that thevirtual ticket voucher is redeemed.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings, wherein likereference numerals designate like structural elements, and in which:

FIG. 1 is a perspective drawing of a gaming system including virtualticket-in and ticket-out services in accordance with the describedembodiments.

FIG. 2 is a block diagram of an electronic gaming machine configured forvirtual ticket-in and ticket-out services in accordance with thedescribed embodiments.

FIG. 3A is a block diagram of an electronic gaming machine including aretrofit device for providing virtual ticket-in and ticket-out servicesin accordance with the described embodiments.

FIG. 3B is a block diagram of an electronic gaming machine including abill acceptor and a printer for providing virtual ticket-in andticket-out services in accordance with the described embodiments.

FIG. 4A shows a block diagram of a system including remote creation,validation and redemption of virtual tickets in accordance with thedescribed embodiments.

FIGS. 4B and 4C show block diagrams of an application for managingvirtual tickets on a portable electronic device in accordance with thedescribed embodiments.

FIG. 5A is a method in a gaming machine for redeeming virtual ticketvouchers in accordance with the described embodiments.

FIG. 5B is a method in a gaming machine for issuing virtual ticketvouchers on a gaming machine.

FIG. 6 shows a block diagram of a gaming device in accordance with thedescribed embodiments.

FIG. 7 shows a perspective drawing of a gaming device in accordance withthe described embodiments.

DESCRIBED EMBODIMENTS

In the following paper, numerous specific details are set forth toprovide a thorough understanding of the concepts underlying thedescribed embodiments. It will be apparent, however, to one skilled inthe art that the described embodiments may be practiced without some orall of these specific details. In other instances, well known processsteps have not been described in detail in order to avoid unnecessarilyobscuring the underlying concepts.

A gaming system compatible with portable electronic devices controlledby users of the gaming system is described. In one embodiment, theportable electronic devices can be configured to store and transmitvirtual ticket voucher information to an EGM or a redemption kiosk andreceive virtual ticket voucher information associated with a virtualticket voucher issued from the EGM. The virtual ticket vouchers can beredeemed on the EGM for credits used to place wagers on a game of chanceor can be redeemed for cash at a redemption kiosk. The EGM can beconfigured to issue virtual ticket vouchers to transfer credits from theEGM. In one embodiment, the virtual ticket vouchers can be madecompatible with existing cashless handling systems that provide for theissuance and redemption of printed ticket vouchers with littlemodification to the existing cashless handling system. Thus, thecashless system can be configured to provide for the validation,redemption and issuance of both printed ticket vouchers and virtualticket vouchers.

With respect to the following figures, methods and apparatus that allowa cashless system to include virtual ticket vouchers is described. Inparticular, with respect to FIG. 1 and interactions between a portableelectronic device and an EGM with a game controller configured toprovide virtual ticket-in and ticket-out services are described. Withrespect to FIGS. 3A and 3B, an EGM retrofitted with one or more devicesthat provide virtual ticket-in and/or virtual ticket-out services isdescribed. With respect to FIG. 4A interactions between a portableelectronic device and a remote server that provides virtual ticketvoucher issuance and redemption capabilities is described. A vouchermanagement application for managing virtual ticket vouchers on aportable electronic device is described with respect to FIGS. 4B and 4C.Methods of issuing and redeeming virtual ticket vouchers in an EGM aredescribed with respect to FIGS. 5A and 5B. Finally, details of gamingdevices and gaming systems compatible with virtual ticket-in and virtualticket-out services are described.

External Interface and EGM-Portable Device Interactions

FIG. 1 is a perspective drawing of a gaming system including virtualticket-in and ticket-out services in accordance with the describedembodiments. For the purposes of illustration, a gaming system server 10is shown connected to an electronic gaming machine (EGM) 2. In otherembodiments, the EGM 2 can be connected to multiple servers and thegaming system server 10 can be connected to multiple EGMs. EGM 2 isconfigured to communicate with a portable electronic device 34. Further,one or more gaming system servers, such as 10, can be configured tocommunicate with portable electronic devices, such as 34.

On the EGM, the communication with the portable electronic device canoccur through a wireless or a wired interface. In various embodiments,for the purposes of communicating with a portable electronic device, theEGM 2 can configured with a single wireless interface but no wiredinterfaces, multiple wireless interfaces but no wired interfaces, asingle wired interface but no wireless interfaces, multiple wiredinterfaces but no wireless interfaces or a combination of wireless andwired interfaces. Thus, the communication interfaces described withrespect to FIG. 1 are for the purposes of illustration and are not meantto be limiting.

In a particular embodiment, one or more of the wired or wirelessinterfaces can be dedicated to operator functions and may only recognizeparticular devices carried by an operator. For instance, a wirelessinterface can be dedicated to allowing an operator perform maintenancefunctions, such as receiving diagnostic information from the EGM. Inanother example, a wireless interface can be dedicated towardsperforming operator functions, such as placing the EGM in a disputeresolution mode, a hand-pay mode or a W-2 (tax requirement) mode. Again,the EGM can be configured to recognize particular operator registereddevices via this interface. In yet another example, a wireless interfacecan dedicated only to premium customers. Via the dedicated wirelessinterface and their portable electronic device, a premium customer maybe able to access to certain functions on the EGM that are not availableto other customers.

As will be discussed in more detail below, one or more of the wirelessor wired interface can be used for transactions involving cash handlingon the EGM 2. An interface can be dedicated for this purpose. Forinstance, a dedicated cash handling interface can be configured only toreceive information associated with cash handling. In other embodiments,a wired or wireless interface on the EGM can be used for cash handlingtransactions with the portable electronic device as well as more generalcommunications, such as transferring information that can be used in aloyalty program or a social media application.

As follows, the EGM 2 is briefly described and then cash handlinginteractions involving a portable electronic device 34, the EGM 2 andgaming system server 10 are discussed. Additional details of the EGM aredescribed with respect to FIGS. 6 and 7. The EGM 2 can include multipledisplays, such as displays 14 and 16. The displays can be used to outputvideo images associated with a wager-based game play, such as apresentation associated with a main game or a bonus game. Game playdecisions can be entered via a player input panel 28. In addition,displays 14 and/or 16 can be provided with a touch screen interface andan associated touch screen controller. The touch screen interfaces canbe used to enter information about decisions associated with game playas well as information associated with other functions offered on agaming machine.

The EGM 2 can include a number of devices used in cash handlingtransactions. The cash handling devices can include 1) a bill acceptor22 configured to accept cash and/or ticket vouchers, a printer 38configured to generate printed ticket vouchers and 3) a card reader 36which can be configured to read a magnetic striped card or a smart card.The magnetic striped card or the smart card can be used to transferfunds, such as funds stored on a debit card. Further, the card reader 36can be used to read account information associated with a loyaltyprogram account.

In a particular embodiment, a wireless interface 18 can be configured toreceive information, such as information associated with a virtualticket voucher, from a portable electronic device 34. As an example, thewireless interface 18 can be configured to implement a near fieldcommunication (NFC) protocol. The NFC protocol is designed with acommunication range of 4 cm or less. NFC operates at 13.56 MHz onISO/IEC 18000-3 air interface and at rates ranging from 106 kbit/s to848 kbit/s. NFC can involve an initiator and a target. The initiatoractively generates an RF field that can power a passive target. Thisenables NFC targets to take very simple form factors such as tags,stickers, key fobs, or cards that do not require batteries. NFCpeer-to-peer communication is of course possible, where both devices arepowered. For instance, the electronic device 34 and EGM 2 can beconfigured to implement a peer-to-peer communication.

Wireless interface 18 can be also used to accept information from adigital wallet application, such an E-wallet application. E-wallets canstore passwords, credit card numbers, email contacts and identificationdata like driver's license or social security numbers. In someinstances, an E-wallet can be linked to a bank account. In theembodiments described herein, an E-wallet application can be used totransfer “cash” electronically to an EGM that can be used for wagers.When funds are received electronically, such as via an E-wallettransaction, the EGM 2 can be configured to store an electronic recordof the transaction in a manner similar to cash transactions involvingphysical currency.

As is discussed in more detail with respect to FIGS. 6 and 7, otherwireless interface protocols can also be implemented on EGM 2. Forinstance, the EGM 2 can be configured to provide Wi-Fi and/or Bluetooth™communications. These protocols can be used in lieu of or in combinationwith NFC. For instance, an NFC communication can be used to instantiatea Wi-Fi or Bluetooth™ communication between the EGM 2 and portableelectronic device 34, such as secure pairing using one of theseprotocols. Further details of device pairing are described below withrespect to FIG. 2.

In particular embodiments, the portable electronic device 34 can beconfigured with an application that manages virtual ticket vouchers thatare redeemable for game play. On the gaming system side, the virtualticket vouchers can be generated in a manner similar to printed ticketvouchers. With printed ticket voucher, a gaming system server, such as10, can be configured to generate and store a validation numberassociated with a particular amount of cash or credits. The validationnumber and the amount associated with the validation number can bestored in a ticket voucher database. The validation number and theamount associated with the validation are stored so that when the ticketvoucher is later presented for redemption it can be validated. Thevalidation can be performed by the gaming system server or anotherdevice in the gaming system.

Next, the gaming system server can send information that allows thevalidation number to be located in the ticket voucher database to theEGM 2. Via the printer 38, the information that allows the ticketvoucher to be located in the ticket voucher database and the amountassociated with the ticket voucher can be printed on a blank ticketvoucher and then output. The information can be printed in differentformats, such as in a text format and/or in a symbol format, such as abar-code. Later, to redeem the ticket, information stored on the printedticket voucher can be read and parsed at an EGM, a redemption kiosk or acashier station. The information read from the ticket can be compared toinformation stored in server 10 when the ticket voucher was created. Ifthe server determines information matches and the ticket voucher hasn'tbe previously redeemed, then the ticket voucher can be redeemed for cashor additional game play.

Similar to a printed ticket voucher, to generate a virtual ticketvoucher, the EGM 2 can send a request to server 10 to generate a uniqueidentification number for a cash amount to be transferred off of the EGM2. Alternatively, the EGM 2 or some other device can generate the uniqueidentification number that is sent to sever 2. The gaming system servercan store the identification number and the cash amount associated withthe ticket as well as the unique information associated with the EGM 2.The unique EGM information can be later used for reconciliationpurposes. Then, the unique identification number can be sent to the EGM2.

As described above, the virtual ticket vouchers and printed ticketvouchers can be generated in the same manner and with littlemodification to an existing cashless system. However, there are somepossible differences as described as follows. One difference can be thatthe server 10 is configured to record whether the ticket voucher isissued as a printed ticket or a virtual ticket. Printed ticket voucherscan include an identification number, such as xx-xxxxxx-xx. Theidentification number can be modified to indicate whether it isassociated with a virtual ticket voucher or a printed ticket voucher.For instance, 01-xxxxxx-xx can be used for printed ticket vouchers while02-xxxxxx-xx can be used for virtual ticket vouchers.

A determination of whether the ticket voucher is generated as a virtualticket voucher or printed ticket voucher can occur on the EGM 2. Adefault position of the EGM 2 can be to generate a printed ticketvoucher if a requested virtual ticket voucher is not successfullygenerated. For instance, as is described in more detail below, canrequest a virtual ticket voucher accidently, cancel it and request aprinted ticket voucher. Thus, an indication of whether the requestedvirtual ticket voucher is issued as virtual ticket or a printed ticketvoucher can be received at the server in an acknowledgement the EGM 2and the server can change the format in which the ticket voucher hasbeen issued if it has changed.

Denoting whether the ticket voucher is a printed or a virtual ticketvoucher can be important for record keeping purposes. In the case of aredeemed printed ticket voucher, it is expected that there will be acorresponding piece of paper when the ticket is redeemed. For virtualprinted tickets, there may not be such a record. For instance, when aprinted ticket is redeemed at an EGM, it is expected that when the cashbox is subsequently removed from the EGM, the cash box includes theprinted ticket. The presence or non-presence of the printed ticket canbe identified in a soft count when the cash in the cash box is counted.

A soft count is one process for counting banknotes in a casino or bank.The soft count rooms are usually among the most secure places due to thelarge amounts of cash that can be on hand at any one time. The countingis usually done by accounting professionals called soft counters, usingcomputer spreadsheets. Typically, a soft count room contains a largetable upon which the currency to be counted is placed, known as the“count table”. Count room personnel manually organize the currency sothat it can be easily counted by hand or by a counting machine. Mostmodern count rooms are equipped with high-speed computerized machinesthat perform the counting process.

In a particular embodiment, the cash box on the EGM 2 can be equippedwith a memory. Virtual ticket voucher information can be loaded to thememory as virtual ticket voucher information tickets are redeemed at theEGM 2. The bill acceptor or the EGM 2 can be configured to transfer thisinformation to the memory. The memory may also include a record of theprinted ticket vouchers received into the cash box. Further, it caninclude a combined transaction list including cash transactions, printedticketed transaction and virtual ticket transactions in the order inwhich they were generated. When the cash box is removed and the billsand printed ticket vouchers are counted, the memory on the cash box canbe interrogated for virtual ticket voucher information and othertransaction information, if it is stored, as part of the soft countprocess. Thus, the cash box can have a complete record of cash andticket vouchers accepted at the EGM 2 where a portion of the ticketvouchers can be printed ticket vouchers and a portion of the ticketvouchers can be virtual ticket vouchers stored electronically.

If desired, equivalent printed vouchers can be generated from thevirtual ticket voucher information to be used as part of the soft countprocess from the information stored in the cash box. For instance, thecash box can be connected to a printer where sheets including one or ofthe virtual ticket vouchers can be generated. For example, 4 ticketvouchers per sheet or 8 ticket vouchers per sheet can be generated. Thevirtual ticket vouchers can be output in a format similar to a printedticket voucher, such as including a bar-code and other informationnormally included on a printed ticket. The printed sheets includingvirtual ticket information can be stored for some time period forauditing purposes.

In one embodiment, the virtual ticket voucher can be created in responseto receiving an input from the E-cash out button 26. After the E-cashout button activation is detected, if credits remain on the EGM 2, theEGM 2 can be configured to send the request for the unique validationnumber and cash amount for the voucher to server 10 via connection 12.In response, the EGM 2 can receive the unique validation number from theserver 10. Based upon the information received from the server, the EGMcan generate a virtual ticket voucher.

In one embodiment, an image of the virtual ticket voucher can begenerated and output to a display on the EGM 2, such as 14 and 16. As anexample, an image of a virtual ticket voucher 40 is shown. The front ofthe virtual ticket voucher can be displayed or the front and back of thevirtual ticket voucher can be displayed. In one embodiment, a virtualticket voucher that is displayed can be formatted in the same manner asa printed ticket voucher, such that it looks like a printed ticketvoucher. For instance, the front of the printed ticket voucher mightinclude a bar-code, a cash value, a location where it was issued, aunique identification number. The back of the ticket can include adisclaimer such as,

-   -   “This ticket is a bearer instrument. The operator is not        responsible for lost or stolen tickets. The player is        responsible for checking this ticket for accuracy, including the        date and amounts shown, and must immediately notify an attendant        of any error. Tickets are void if illegible, altered,        counterfeit, incomplete, produced in error, or fail any        validation testing. Neither the operator nor IGT™ shall be        responsible for the issuance, validation or payment of lost,        stolen, counterfeit or multiple EZ Pay cash vouchers. IGT™ and        the operator shall be discharged from any and all liability upon        payment of any claim arising from the redemption of the first        cash voucher presented with a valid bar code. IGT™ and the        operator reserve the right to withhold validation and payment        pending a determination whether the cash voucher has been stolen        or lost”

To prevent someone from taking a picture of the displayed image andconverting it to a virtual ticket voucher and trying to redeem, aportion of information needed to redeem the virtual ticket voucher maynot be displayed. For instance, a second unique validation number can betransmitted from the EGM 2 to the portable electronic device 34 that isneeded to redeem the ticket. This second unique validation number maynot be rendered in the image of the virtual ticket voucher displayed onthe EGM 2. Besides, ticket information, such as a second uniquevalidation number, data can be sent to the portable electronic devicethat allows an image of virtual ticket voucher rendered on EGM 2 to alsobe rendered on the user's portable electronic device.

The format of the images of the virtual ticket voucher can vary fromgaming enterprise to gaming enterprise and can further vary fromlocation to location within the gaming enterprise. Further, the formatof the virtual ticket images can vary from EGM 2 to EGM 2 within alocation if the print capabilities in each EGM are different such thatit affects the format of the printed ticket voucher that is output. Inother embodiments, the generated virtual ticket voucher image displayedon EGM 2 can be different from printed ticket vouchers. For instance,the system can be configured to allow a user to select a custom formatfor their virtual ticket vouchers. The EGM 2 can be configured togenerate and display a custom formatted virtual ticket voucher to thedisplay.

In one embodiment, the custom format virtual ticket voucher informationcan be stored on their portable electronic device 34 and transmitted tothe EGM 2, such as via a wireless or wired communication connect betweendevice 34 and EGM 2. As another example, the custom format virtualticket voucher information can be stored in a loyalty program account ona gaming system server. This information can be retrieved when the userprovides loyalty program account information to the EGM 2. In anotherembodiment, the images of the virtual ticket vouchers that are displayedon the EGM 2 can be a standard format, such as to match the format ofthe printed ticket vouchers issued at the EGM 2. The virtual ticketvoucher information can be transmitted to the user's portable electronicdevice. Then, via an application running on the user's portableelectronic device 34, the user can select a custom format to display thevirtual ticket voucher. In yet other embodiments, the images of thevirtual ticket voucher can be selected to match a theme of the game orreflect a theme associated with a calendar event, such as a holidaythem.

In alternate embodiments, an image of the virtual ticket voucher doesn'thave to be displayed. For instance, a message might be output to display16 of “please retrieve your virtual ticket voucher for X dollars” but animage of the virtual ticket voucher may not be generated. In anotherexample, a bezel 20 around interface 18 may light-up in a particularcolor and/or flash with a particular light pattern to indicate thevirtual ticket voucher is ready. In other embodiments, a combination ofa message, an image of the virtual ticket voucher and/or a lighted bezelcan be used. For instance, a formatted virtual ticket voucher can beoutput can be output to display 16 with a message and the bezel 20 canchange state to indicate that the virtual ticket voucher is ready.

When the virtual ticket voucher is ready, the EGM 2 can indicate it isready to transfer the virtual voucher, such as via changing bezel state20. In response, when a NFC protocol is used, the portable electronicdevice 34 can be brought in proximity to even in contact with the outersurface of interface 18. In one embodiment, for security purposes, avirtual ticket voucher application executed on the portable electronic34 may have to be active for a transaction to take place, i.e., for theportable electronic device 34 to receive virtual ticket voucherinformation from the EGM 2. Similarly, as is described in more detailbelow, the virtual ticket voucher may have to be active on the portableelectronic device 34 to transmit virtual ticket voucher informationstored on the portable electronic device 34 to the EGM 2.

If another wireless protocol with a longer range is utilized or a wiredconnection is utilized, it may not be necessary for the portableelectronic device to be placed in close proximity to interface 18. Inresponse to receiving virtual ticket voucher information from the EGM 2,information about the virtual ticket voucher can be output on thedisplay 32 of the portable electronic device 32. The information that isoutput to display 32 can be selected to match the format of informationoutput to display 16 on the EGM 2. For instance, if a virtual ticketvoucher image is output to display 16, then the virtual voucher imagecan also appear on the user's device after the transfer of information.With virtual ticket voucher information simultaneously output on bothdisplays, the user can compare the images on the display 32 and the EGM2 to visually confirm the successful transfer.

When the virtual ticket voucher is ready and the interface 18 andoptionally the bezel 20 have been activated, the EGM 2 may begin acountdown timer. If a successful transfer is not made to a portableelectronic device, such as 34, within the time period associated withthe countdown timer, the EGM 2 can convert the virtual ticket vouchertransaction to a printed ticket voucher transaction and generate aprinted ticket that is output via the printer 38. If the type of voucher(virtual or printed) is indicated by the identification number on theticket, then the EGM 2 can be configured to alter the identificationnumber that is printed on the printed ticket voucher so that it nowreflects a number that is consistent with a printed ticket voucher. Inaddition, the EGM 2 can contact the server 10 to notify in the change informat and number for the voucher and the server 10 can store thisinformation. In one embodiment, a cancel button can be provided on theEGM 2 that switches a cash out transaction from a virtual ticket voucherto a printed ticket voucher.

A virtual ticket voucher transaction may time out or a user may wish tocancel a virtual ticket voucher for a number a reasons. For instance,the user may cancel because they realize they have forgotten or losttheir phone. In another example, the user may have requested a virtualticket transaction accidently, such as by hitting the E-cash out buttoninstead of the cash out button. In another example, their portableelectronic device 34 may have run out of charge or may not befunctioning properly. In yet another example, the interface 18 may notbe functioning properly, the user's portable electronic device may notbe functioning properly or a combination of problems with the interface18 or the user's portable electronic device may prevent the transactionfrom occurring.

After the virtual ticket voucher is transferred to the user's portableelectronic device, an application executing on the portable electronicdevice can be executed that allows the user to manage their virtualticket vouchers. For instance, as mentioned above, the application mayallow the user to customize the appearance of the virtual ticket voucherin the application. In another example, the application can beconfigured to keep track of when printed ticket vouchers have beenreceived and an expiration date of the ticket. The application can beconfigured to notify the user if a virtual ticket voucher is nearing itsexpiration date. In yet another example, the application can beconfigured to exchange information with an E-wallet application or caninclude E-wallet functionality. In a further example, virtual ticketvoucher information can be stored in the “cloud,” i.e. remotedistributed storage, and the application can be configured to access andretrieve virtual ticket voucher information stored in the “cloud.”Further details of this application are described with respect to FIGS.4B and 4C.

When information is transferred wirelessly between the EGM 2 and theportable electronic device, the EGM 2 can be configured to receive andstore unique device identification information associated with portableelectronic device. Further, the portable electronic device can beconfigured to receive and store information associated with the EGM 2.The EGM 2 can be configured to associate the unique deviceidentification information with the virtual ticket voucher that wasissued. The unique portable device identification information can bestored on the EGM 2 and also sent to a validation server, such as server10, where it can also be associated with the virtual ticket voucherinformation that was generated.

In one embodiment, as a requirement or optionally if the user desires,the unique portable device identification information can be used in theredemption of the virtual ticket voucher. When the virtual ticketvoucher is presented at a redemption device, such as EGM 2, the uniqueidentification information associated with the portable electronicdevice and the unique identification information associated with thevirtual ticket voucher can be received at the redemption device andtransmitted to a validation device, such as server 10. Then, thevalidation device can compare the received virtual ticket voucherinformation and portable electronic device identification information tothe virtual ticket voucher information and portable device informationstored when the virtual ticket voucher was issued. If unique playeridentification information is known, such as information associated witha loyalty program, then this information can also be included in thevalidation process.

When the information matches, then the validation device can send amessage to the redemption device to redeem the virtual ticket voucher atthe amount associated with the virtual ticket voucher. If the portableelectronic device information matches and the virtual ticket voucher hasalready been redeemed, then the validation device can send a message tothe redemption device including this information. In response, theredemption device can display a message, such as ticket previouslyredeemed. If the portable device information doesn't match but thevirtual ticket voucher information matches, the validation device cansend a message to the redemption device regarding this state. Inresponse, in one embodiment, the redemption device can display amessage, such as “Virtual ticket voucher is invalid” or “Deviceinformation is invalid go to the cashier station to redeem the ticket.”At the cashier station, the user may have to present identificationinformation to redeem the virtual ticket voucher that is stored on theportable electronic device with unique device identification informationthat doesn't match the portable electronic device to which the ticketvoucher was issued. If the virtual ticket voucher information doesn'tmatch any of the records on the validation device, then the validationdevice can send a message indicating this state to the redemptiondevice. In response, the redemption device can display a message, suchas “ticket voucher invalid.”

The portable electronic device information received that is gatheredduring an issuance of a virtual ticket voucher or the redemption of avirtual ticket voucher can be used in a dispute resolution process. Apatron may decide that an amount of a virtual ticket voucher transmittedfrom the EGM 2 to the portable electronic device 34 is incorrect or anamount of a virtual ticket voucher transmitted from the portableelectronic device 34 to the EGM 2 is incorrect. In response, the playermay request the presence of an operator. The operator can place the EGM2 in a dispute resolution mode where a record of virtual vouchers issuedfrom the EGM 2 or accepted on the EGM 2 can be accessed.

The dispute resolution mode may allow information regarding virtualticket vouchers issued or accepted at the EGM 2 to be retrieved frommemory and displayed on the EGM 2. The operator may be able scroll theticket voucher records in order of acceptance or issuance. In oneembodiment, a player may be able to couple their portable electronicdevice 34 to the interface 18. In response, the EGM 2 can be configuredto search the stored ticket voucher records and display informationregarding any virtual ticket vouchers issued to the portable electronicdevice 34 or received from the portable electronic device 34. In oneembodiment, the EGM 2 can be configured to reissue a virtual ticketvoucher to the portable electronic device, such as if the playerconvinces the operator that the information regarding a virtual ticketvoucher issued to the portable electronic device has been lost for somereason.

In other embodiments, virtual ticket voucher information can be accessedvia a secondary device, such as a player tracking unit or via a “servicewindow” on the EGM 2. For instance, an electronic log of virtual voucheractivity and/or virtual cash activities can be stored on a remote hostwhich can be accessible via a service window on the EGM 2. Furtherdetails of service windows applications are described below with respectto FIG. 6.

As described above, the redemption of virtual ticket voucher stored on aportable electronic device, such as 34, can involve transferring virtualticket voucher information from the portable electronic device 34 to aredemption device, such as EGM 2. On EGM 2, the cash value associatedwith the virtual ticket voucher can be converted to credits where thecredits can be used for wagers on a game of chance. In one embodiment,the virtual ticket voucher transfer from device 34 to EGM 2 can beinitiated when the EGM 2 detects an actuation of the E-cash-in button24.

In a particular embodiment, restricted credits can be transferred to theEGM 2 via a virtual ticket voucher. For instance, restricted credits canbe transferred to the EGM 2 that are available for wagers but can't beredeemed for cash. In other embodiments, a virtual ticket voucher can beredeemed to unlock a feature on the EGM 2, such as a particular bonusmode. In yet other embodiments, a virtual ticket voucher can be used totransfer information associated with persistent gaming, such as progressor achievements a player has previously obtained playing a game. Inother embodiments, a virtual ticket voucher can be used to 1) transfertax information associated with an EGM pay out, such as a W2G receipt,2) report metering information associated with the EGM 2 and 3) reportdiagnostic information associated with the EGM 2, such as when the EGMis not functioning properly.

In response to detecting the actuation of button 24, the EGM 2 canchange the state of interface 18 so that it is enabled to receive aninformation transfer from a portable electronic device, such as 34.Further, the change in state of the interface 18 can be indicated by achange in state of a status indicator associated with interface 18. Forinstance, a bezel 20 surrounding the interface 18 can be lit up with aparticular color and/or light pattern to indicate the interface 18 isready to receive virtual ticket voucher information. Further, ifenabled, a sound pattern can be emitted from the status indicator toindicate it is ready to receive virtual ticket voucher information froma portable electronic device.

In a particular embodiment, when interface 18 is activated a countdowntime can be started. If the countdown timer reaches a termination value,such a zero, before a communication is established with a portableelectronic device, then the interface 18 can be turned off and thestatus indicator associated with interface 18 can be changed to indicateit is not ready to receive information. For instance, the bezel 20surrounding the interface can be lit up with a particular light patterand/or color to indicate a transition state. In addition, the statusindicator can be configured to indicate the transition from an on stateto and off state is about to occur. For instance, the bezel 20 canchange to a particular color and flash at an increasing rate before theinterface 18 is turned off. A particular sound pattern can also beemitted to indicate the transition.

In other embodiments, the interface 18 can be configured to support anactive communication session between the portable electronic device andthe interface 18. For instance, interface 18 can support NFCcommunications and Bluetooth™ communications. A user can tap a NFC andBluetooth™ enabled device to the interface 18. The tap can transmit, viaNFC, data which allows a Bluetooth™ communication pairing to be set upbetween the portable electronic device and the EGM 2. The communicationpairing can utilize encrypted communications. The status indicator 19can be used to indicate whether the communication pairing is active ornot between the portable electronic device and the EGM 2.

In one embodiment, the application that allows the transfer of thevirtual ticket voucher from the portable electronic device to the EGM 2may have to be active on the portable electronic device 34 before atransfer can occur. Further, a secondary authentication method, such asentering a PIN correctly, may be required on the portable electronicdevice 34 before the transfer is allowed to occur. In one embodiment,the use of a secondary authentication method can be triggered based uponan amount of the ticket voucher that is to be redeemed such thatvouchers above a certain amount require a secondary authentication whilevouchers below a certain amount do not require a secondaryauthentication.

During the redemption process, an image of the virtual ticket voucherthat is to be redeemed can be displayed on the display 32 of theportable electronic device 34. When the virtual ticket voucherinformation is successfully transmitted to EGM 2, it can be displayed onthe EGM 2, such as in an image of a ticket voucher 40. Then, the usercan compare the virtual ticket voucher information displayed on thedisplay 32 to the virtual ticket voucher information displayed ondisplay 16 or some other display on the EGM 2.

In one embodiment, an image data associated with a virtual ticketvoucher and/or formatting information can be transmitted from theportable electronic device 34 to the EGM 2 so that the image rendered onthe EGM 2 appears similar to the image rendered on portable electronicdevice 34. As an example, as described above, an application running onportable electronic device 34 can be configured to allow a user tocustomize the appearance of virtual ticket vouchers displayed on theirdevice. Thus, some of the custom formatting information related to thevirtual ticket voucher appearance can be transferred from the portableelectronic device to the EGM.

In another embodiment, the image rendered of a virtual ticket vouchercan be a standard format that is not affected by formatting informationreceived from the portable electronic. As described above, the onlyfront of the virtual ticket voucher or the front and back of the virtualticket voucher can be rendered on a display on the EGM 2. In addition asdescribed above, an image of the virtual ticket voucher doesn't have tobe rendered on the EGM 2. For instance, when a virtual ticket voucher isaccepted, the EGM 2 can be configured to display a message such as“virtual ticket voucher for x dollars received” where “x” is the amountassociated with the ticket.

After the virtual ticket voucher is successfully received, the EGM 2 cansend received virtual ticket information to a validation device, such asgaming system server 10. The validation device can determine whether theinformation associated with the virtual ticket voucher is associatedwith a valid virtual ticket voucher that hasn't already been redeemed.When the information is valid, the validation device can send a messageto the redemption device, such as EGM 2, to redeem the virtual ticketvoucher for an amount that the validation server determines isassociated with the virtual ticket voucher.

The redemption device can receive the message from the validation deviceand in response, redeem the ticket in some manner. For instance, in thecase of the EGM 2, the ticket can be redeemed for credits. As anotherexample, a redemption kiosk, in response to receiving a validationmessage can dispense the cash amount associated with the virtual ticketvoucher. After redeeming the virtual ticket voucher, the redemptiondevice can send a message to the validation device indicating it hassuccessfully redeemed the virtual ticket voucher. In response, thevalidation device can store information indicating the virtual ticketvoucher has been redeemed. Thus, if the person controlling the portableelectronic device attempts to redeem the virtual ticket voucher again,the validation device can be configured to indicate the transaction isinvalid because the virtual ticket voucher has been previously redeemed.The redemption device, such as EGM 2, can be configured to storeinformation regarding the virtual ticket voucher that has been receivedand optionally unique device identification information from theportable electronic device that transmitted the virtual ticket voucherinformation to the redemption device. The redemption device can also beconfigured to send the portable electronic device information to aremote device, such as server 10.

There are a number of potential advantages of providing virtual ticketvoucher functionality on an EGM. In the case of virtual ticket voucherissuance, one advantage is that the stack of blank tickets used togenerate printed ticket vouchers may have to be refilled lessfrequently. This reduces the material costs associated with purchasingtickets and the labor costs associated with refilling the blank ticketstack because the rate at which printed tickets are generated isreduced. Further, it is better for the environment since less paper isused. In the case of virtual ticket voucher redemption, one advantage isthat the cash box associated with the bill/ticket acceptor may fill upmore slowly. Thus, the labor costs associated with removing andreplacing a full cash box can be reduced since the cash box will fill upmore slowly. Further, the soft count process can be simplified reducinglabor costs because less printed tickets need to be handled during thesoft count process.

Internal Device Control

Next details of internal configurations of an EGM configured to redeemand/or issue virtual ticket vouchers are described. With respect to FIG.2, an EGM with a game controller modified to redeem and/or issue virtualticket vouchers is discussed. With respect to FIGS. 3A and 3B, EGMs aredescribed where the game controller remains unmodified and where virtualticket-in/ticket-out functions are performed by retrofit devices, suchas a retrofit printer and/or a retrofit bill/ticket acceptor. FIG. 2 isa block diagram of an electronic gaming machine 2 configured for virtualticket-in and ticket-out services.

The EGM 2 is coupled to a validation server 68 and an accounting server70 via a network interface 56. The validation server 68 can beconfigured to 1) generate validation numbers for printed and virtualticket vouchers issued at EGM 2 and 2) validate virtual ticket andprinted ticket vouchers received at the EGM 2. The validation server 68can be part of a cashless system. The accounting server 70 can beconfigured to receive accounting information, such as coin-in/coin-out,from the EGM 2. The accounting server 70 can be part of a loyaltyprogram system where members can earn points redeemable for comps basedupon their game play. In one embodiment, the network interface 56 can bea smart interface board (SMIB) associated with a player tracking system.

The virtual ticket voucher processing, involving such steps asvalidation, redemption and issuance of virtual ticket vouchers describedabove with respect to FIG. 1, can be handled by the virtual voucherprocessing logic 74 on the game controller 50. The control of thewireless interface 18, such as powering it on and off in response tocertain events, establishing communication sessions with portableelectronic devices and sending information via the wireless interface18, can be handled by the wireless interface control 72. As describedabove, the EGM 2 can include multiple wireless interfaces and gamecontroller 50 can be configured to communicate using multiple wirelesscommunication protocols.

Virtual ticket voucher information can be transmitted and received viathe wireless interface 18. In one embodiment, the wireless interface 18can be integrated into the cabinet of the EGM 2 (e.g., see FIG. 1) andgame controller 50 can be configured to communicate directly with andsend control commands to the wireless interface 18. In otherembodiments, the wireless interface 18 can be integrated into a devicemounted to and/or within the gaming machine cabinet, such as the printer38, the bill validator/voucher acceptor 22, a card reader (not shown) ora player tracking unit (not shown). For instance, a wireless interface18 can be integrated into a bezel surrounding a printer slot, a cardreader slot or a bill/ticket acceptor slot. In yet another example, thewireless interface can be integrated into a player tracking unit.

In the embodiments where the wireless interface is embedded in asecondary device, such as a printer or a player tracking unit, the gamecontroller 50 can optionally communicate via the wireless interface andsend control commands to control the wireless interface via a secondarycontroller, such as printer controller or a player tracking controller.For instance, the game controller 50 can detect an actuation of theE-cash out button 26 and then send a command to the secondary deviceincluding the wireless interface to turn on the wireless interface. Inthe secondary device, a secondary device controller can simple forwardthe command to the wireless interface 18, which can be configured torespond to the command from the game controller 50. In another example,the secondary device controller can be configured to interpret thecommand received by the game controller 50 where the command received bythe game controller can be at a high level and not understood by thewireless interface 18. From the high-level command received from thegame controller 50, the secondary device controller can generate alow-level command understood by the wireless interface 18 that isincorporated in the secondary device.

In other embodiments, a secondary device can include virtual ticketvoucher processing logic executed by a secondary controller. Forinstance, the printer 38 can include a printer controller capable ofexecuting virtual ticket voucher processing logic and printed ticketlogic and a wireless interface (Other examples of secondary devices withthis capability can include but are not limited to a player trackingunit, a card reader or a bill validator). The game controller 50 can beconfigured to detect an actuation of the E-cash out button 26. Inresponse, the game controller 50 can send a high-level message to theprinter 38, such as “generate a virtual ticket voucher of a particularamount.” In response to receiving the command from the game controller50, the printer controller can generate low-level commands to controlvarious devices on the printer that allow the high-level command to beimplemented. For instance, the printer controller can generate commandsthat 1) turn-on the wireless interface on the printer and change astatus of a status indicator for the wireless interface on the printerto indicate it is “on,” 2) receive device information from a portableelectronic device and then construct and send a message that allows avirtual ticket voucher to be sent to the portable electronic device and3) send an acknowledgement to the game controller when the virtualticket voucher has been received. The acknowledgement can include uniqueidentifier information associated with the portable electronic devicethat received the virtual ticket voucher.

The game controller 50 can be configured to logically recognize asecondary device with multiple functions as separate devices accordingto the functions. The game controller 50 can recognize the devicesduring a device enumeration process. For example, a card reader withcard reader functions and a capability to accept virtual ticket voucherscan present itself to the game controller 50 as a card reader 50 and abill validator that accept virtual ticket vouchers. In this example, thegame controller 50 may have already enumerated a first bill validatorthat accepts only cash and printed tickets. Thus, after the enumerationprocess, the game controller can logically be configured to control acard reader, a first bill validator that accepts cash and printedtickets and a second bill validator that accepts virtual ticketvouchers.

In yet other embodiments, the virtual ticketing voucher processing logicexecuted on a secondary device can be transparent to the game controlcontroller 50. For example, the game controller 50 may be simplyconfigured to send a “print ticket voucher” command and the secondarycontroller can be configured to issue the ticket voucher as a virtualticket voucher. For instance, a card reader with this capability canreceive the “print ticket voucher” command and issue a virtual ticketvoucher. The card reader can be configured to communicate with a remotehost to receive ticket validation numbers to associate with the virtualticket voucher and report the issuance of the virtual ticket voucher tothe remote host. If the card reader is not able to issue the virtualticket voucher and a printer is present, the card reader can forward thecommand to the printer to have it issue a printed ticket voucher.

If the game controller 50 doesn't receive an acknowledgement within sometime period, the game controller 50 can send a command to the printer tocancel the virtual ticket voucher transaction and generate a printedvoucher for the amount. In response, the printer controller can turn-offthe wireless interface and change the status indicator for the wirelessinterface to indicate it is no longer on. Then, the printer controllercan control various print devices used to issue a printed ticketvoucher.

Returning to FIG. 2, in various embodiments, the wireless interface 18can include a wireless interface controller (not shown) separate fromthe game controller 50 for processing signals received at the wirelessinterface and for controlling signals emitted by the interface. Thewireless interface controller can be configured to communicate directlywith the game controller 50 or can communicate with a secondarycontroller that acts as an intermediary between the game controller 50and the wireless controller. Via the interface 18, information 34regarding electronic cash transfers and virtual can be received andinformation 35 regarding virtual ticket vouchers. The received signals,such as signals associated with a virtual ticket voucher, can be parsedfor information according to a particular wireless communicationprotocol, such as an NFC protocol. The parsing of information fromreceived wireless signal data can be done within the wireless interfaceand then sent to the game controller 50 or the signal data can be sentthe game controller 50 or a secondary controller and parsed within thegame controller 50 or secondary controller (not shown).

The interface 18 can be configured to send information formatted in oneor more different wireless communication protocols. For instance, asdescribed above, the EGM 2 via the wireless interface 18 can beconfigured to communicate information formatted in a NFC compatibleprotocol. Although not shown, a wired connection can be used to receivevirtual ticket voucher information as well as other types of informationfrom a wired interface coupled to a portable electronic device. Thecommunication protocol used for the wired communication connection canvary depending on the wired connection that is utilized. In oneembodiment, it can be USB. In a particular embodiment, the physicalconnection can be a micro USB compatible connection.

In other embodiments embodiment, an NFC interface on an EGM 2 can beused to set-up a higher speed communication between the EGM 2 andanother NFC enabled device such as smart phone. The higher speedcommunications can occur via wireless interface 18 or another wirelessinterface on the EGM 2. The higher speed communication rates can be usedfor expanded content sharing. For instance, a NFC and Bluetooth enabledEGM can be tapped by an NFC and Bluetooth enabled smart phone toinstantiate Bluetooth pairing between the devices. Instantiating pairingbetween a gaming device and an NFC enabled device, such as a smartphone,in this manner can save time related to searching, waiting, and enteringcodes. In another example, a gaming device can be configured as an NFCenabled router, such as a router supporting a Wi-Fi communicationstandard. Tapping an NFC enabled device to an NFC enabled and Wi-Fienabled gaming device can be used to establish a Wi-Fi connectionbetween the two devices.

As described above, the NFC communication can be used to exchangeinformation to allow pairing to be established between a user-controlleddevice and the EGM 2. For instance, Bluetooth™ pairing occurs when twoBluetooth devices agree to communicate with each other and establish aconnection. In order to pair two Bluetooth wireless devices, a password(passkey) is exchanged between the two devices. The Passkey is a codeshared by both Bluetooth devices, which proves that both users haveagreed to pair with each other. After the passkey code is exchanged, anencrypted communication can be set up between the pair devices. In Wi-Fiparing, every pairing can be set up with WPA2 encryption or another typeof encryption scheme to keep the transfer private. Wi-Fi Direct is anexample of a protocol that can be used to establish point-to-pointcommunications between two Wi-Fi devices. The protocol allows for aWi-Fi device pair directly with another without having to first join alocal network. The method makes it possible to share media from a phone,play multiplayer games or otherwise communicate directly, even when norouter exists. Via pairing between the EGM 2 and a portable electronicdevice, a portable electronic device may be able to utilize some of thefunctionality of secondary devices residing on the EGM 2. For instance,it may be possible for a player to print something from their portableelectronic device using the printer 38 on the EGM 2 when it is paired tothe EGM 2.

The game controller 50 can be used to control a status of the wirelessinterface 18, such as an “on” status where it is operable to receivewirelessly transmitted information from a portable electronic device oran “off” status where it is not operable to receive information. Inparticular embodiments, the game controller 50 can be configured to turnon the wireless interface in response to detecting an actuation of anE-cash in button 24 or an E-cash out button 26 (The actuation of thebuttons can generate a signal which is received by the controller 50).In various embodiments, the E-cash in button or the E-cash out buttoncan be integrated into a player input panel on the EGM cabinet. Further,the E-cash in button 24 and/or the E-cash out button 26 can beintegrated into a secondary device, such as on the printer 38, the billvalidator/voucher acceptor 22, a card reader (not shown) or a playertracking unit (not shown).

The status of the wireless interface 18 and upcoming changes in statusto the wireless interface 18 can be indicated by an interface statusdevice 19. The interface status device 19 can include components, suchas lights and/or audio devices. The game controller 50 can be configuredto control the interface status device 19 in a way that indicates thestate of the wireless interface 18, such as on, off and about to changefrom on to off. As noted above, the control can be direct or via anintermediary device, such as a secondary controller.

Metering

For accounting and regulatory purposes, the game controller 50 can beconfigured to update and maintain a variety of hard and soft meters onthe EGM. The hard and soft meters can be affected by transactionsinvolving virtual ticket vouchers. A hard meter can be anelectro-mechanical device, like an odometer, with a display thatadvances to display a quantity. Usually, a hard meter is not resettable.Government regulations, which can vary from jurisdiction tojurisdiction, often require hard meters to be read on a regular basis,such as monthly. Examples of hard meters 84 can include coins-in 84 a,coins-out 84 b, coins-dropped 84 c, jackpots-paid 84 d and cancelledcredit meter 84 e. Other hard meters can be implemented and these areprovided for the purposes of illustration only.

The game controller 50 can be configured to update the coins-in meter 84a in response to value-in transactions. For example, the coins-in meter84 a can accumulate all value-in transaction on the EGM 2, such as fromcoin, bills, credit, token, paper token, printed ticket vouchers andvirtual ticket voucher transactions. Thus, when a virtual ticket voucheris accepted on the EGM 2, the coins-in meter 84 a can be updated by someamount depending on the value of the virtual ticket voucher. Devices,such as but not limited to the wireless interface 18, the billvalidator/voucher acceptor 22 and a coin acceptor (not shown) can beused in performing a value-in transaction. In addition, via the networkinterface 56, the game controller 50 can be configured to receive atransfer of value, such as credits, to the EGM 2, from a remote devicesuch as a bonusing server.

The game controller 50 can be configured to update the coins-out meter84 b in response to value-out transactions for the player. The coins-outmeter 84 b can be configured accumulate all value-out transactions fromthe EGM 2, such as from outgoing coin, bills, token, credit, papertoken, hopper ticket, printed ticket voucher and virtual ticket vouchertransactions, paid out for a) awards and b) credits from awards that arewagered. Thus, when a virtual ticket voucher is issued from the EGM 2,the coins-out meter 84 b can be updated by some amount depending on thevalue of the virtual ticket voucher. Devices, such as but not limited toa coin-hopper (not shown), wireless interface 18 and printer 38 cangenerate the value-out transactions. The coins-out meter 84 b mayinclude credits that are accumulated on the jackpots-paid meter 84 d.

The game controller 50 can be configured to update the coins-droppedmeter 84 b in response to value-out transactions for the casino. Thecoins-dropped meter 84 d can accumulate 1) all coins and tokens thathave been diverted into a drop bucket and 2) bills, paper tokens,printed ticket vouchers and virtual ticket vouchers accepted by the EGM2. Thus, coins-dropped meter 84 d can be advanced when a virtual ticketvoucher is accepted at the EGM 2.

The jackpots-paid meter 84 d can reflect any single event award that isnot paid out by the EGM 2. For example, depending on the amount of thejackpot, the EGM 2 may not be configured to dispense coins, issue aprinted ticket voucher or issue a virtual ticket voucher above a certainvalue. In this situation, the payment of the jackpot amount can behandled by some other means, such as check from the casino. Thejackpots-paid meter 84 d may also include credits accumulated on thecanceled credit meter. The canceled credit meter 84 e can accumulatecredits paid by means other than payouts from the devices on the EGM 2,such as the hopper, printer, bill hopper, wireless interface or jackpotpayouts if the device has such credit provisions.

The game controller 50 can be configured to maintain a number of softmeters. The soft meters can be electronic equivalents to the hard meterswhere data is stored in a digital format. The soft meters can bedesigned to be maintained at all times even when the EGM 2 is notsupplied with power. One type of memory that can be used for storingsoft meter data is a non-volatile memory, such as a battery backed RAM.It may be possible to reset the soft meters. For instance, thenon-volatile memory storing the soft meter data can be cleared to resetthe soft meters. However, before it is implemented, this process mayrequire approval from a gaming regulator. Further, the EGM 2 can bedesigned such that an error condition on the EGM 2, such as a powerfailure, doesn't cause the soft meters stored in non-volatile memory tobe erased.

The EGM 2 can be configured to maintain soft meters that duplicate allor a portion of the quantities accumulated by the hard meters 84. Forinstance, the game controller 50 can maintain a soft coin-in meter 62.When duplicate values are accumulated on the soft and hard meters, thevalues accumulated over a particular time period on each type of metershould match. As described above, the soft meters that duplicate of thehard meters can be affected when virtual ticket vouchers are redeemedfor credit on the EGM 2 or when virtual ticket vouchers are issued. Forinstance, the coin-in soft meter 62 and coins-dropped soft meter (notshown) can be updated in response to the successful redemption of avirtual ticket voucher. As another example, the coin-out soft meter (notshown) can be updated in response to a successful acceptance of virtualticket voucher.

The game controller 50 can include an operator mode 58 where values ofthe soft meters can be read. The operator mode 58 includes the softwarelogic that allows values of the soft meters to be gathered and thenoutput. For instance, in operator mode, the game controller 50 candisplay the values of various soft meters to the main display. In someembodiments, the game controller 58 can be configured to periodicallysend values of the soft meters to a remote device, such as accountingserver 70. In another embodiment, the soft meter values can be displayedvia a secondary device. For instance, a player tracking unit with adisplay and a smart interface board (SMIB), coupled to the gamecontroller 50 can be configured to retrieve soft meter data from thegame controller 50 and display it to the player tracking display. Asanother example, a SMIB coupled to the game controller 50 can be used tostore and report soft meter values to a remote device.

The EGM 2 can accumulate other quantities in the soft meters that arenot accumulated by the hard meters 84. For instance, in one embodiment,the game controller 50 can maintain a voucher-in soft meter 64. Thevoucher-in soft meter 64 can record a total number of validated printedticket vouchers and validated virtual ticket vouchers redeemed the EGM2. Thus, the voucher-in soft meter 64 can be incremented by 1 each timea printed or virtual ticket voucher is redeemed. The voucher-out softmeter 66 can record a total number of printed ticket vouchers andvirtual ticket vouchers issued from the EGM 2. Thus, voucher-out softmeter 66 can be incremented by 1 each time a printed ticket voucher or avirtual ticket voucher is issued from the EGM 2.

As another example, the game controller 50 can maintain a virtual ticketvoucher-in soft meter 80 and a virtual ticket voucher-out soft meter 82.The virtual ticket voucher out meter can be advanced by 1 each time avirtual ticket voucher is issued from the EGM 2. The virtual ticket inmeter can be advanced by 1 each time virtual ticket voucher is acceptedby the EGM 2. Other soft meters (not shown) can include a total value ofvirtual ticket vouchers issued, a total value of virtual ticket vouchersand printed ticket vouchers issued, a total value of virtual ticketvouchers successfully redeemed and a total value of the virtual ticketvouchers and a printed ticket vouchers successfully redeemed. Thus, asvirtual ticket vouchers are successfully redeemed and virtual ticketvouchers are successfully issued, these four soft meters can beincremented depending on values associated with each of the virtualticket vouchers issued or redeemed. The game controller 50 can alsoreport soft meter values including each time a soft meter is incrementedto a remote device for cross validation accounting purposes.

Dispute Resolution

At certain times, a player can dispute a transaction that has occurredon an EGM. For instance, a player can dispute that the EGM 2 issued avirtual ticket voucher that didn't accurately reflect the credits thatwere on the EGM 2 at the time the virtual ticket voucher was issued. Inanother embodiment, the player can dispute that the credits associatedwith a virtual ticket voucher accepted at the EGM 2 were not properlycredited to the EGM. In one embodiment, to allow for disputes involvingvirtual ticket vouchers, an operator activated dispute resolution modecan be provided on the game controller.

In one embodiment, to help with dispute resolution, the game controller50 can maintain a virtual ticket voucher received stack 60 and a virtualticket voucher issued stack 61. The virtual ticket voucher receivedstack 60 can include an electronic log of information associated withvirtual ticket vouchers, such as time received, amount associated withthe voucher, virtual ticket voucher number, when the virtual ticketvoucher was issued, etc. In addition, the virtual ticket voucherreceived stack 60 can include images of virtual ticket vouchers redeemedand validated on the EGM 2. As described above, in one embodiment, whena virtual ticket voucher is received, the game controller 50 can beconfigured to render an image of the received voucher. Thus, the imagethat is rendered can also be saved to the virtual ticket stack 60. Thevirtual ticket voucher images can be saved with the time that they arereceived.

When placed in dispute resolution mode, the game controller 50 can beconfigured to display one or more of the saved virtual ticket voucherimages at a time to a display, such as a main display on the EGM 2. Inone embodiment, a virtual ticket voucher image is saved when the virtualticket voucher is accepted. In another embodiment, an image of thevirtual ticket voucher can be rendered on the fly based upon virtualticket voucher information saved to an electronic log, such as a ticketformat, ticket number, ticket amount, etc. The dispute resolution modecan provide an interface that allows the operator to scroll through thevirtual ticket voucher received stack 60, such as in the order that thevirtual ticket vouchers were received. In another embodiment, thedispute resolution mode can be configured to display virtual ticketvoucher information, such as the amounts associated with each virtualticket voucher received, in a non-image format. A benefit of displayingthe information in an image format is that the customer may recognizethe image of the voucher which can aid the dispute resolution process.

In another embodiment, data used to render a virtual ticket voucher canbe saved. For example, if a standard format is used to render thevirtual ticket received vouchers, the saved data may be the unique dataassociated with each virtual ticket voucher, such as an amount, ticketnumber, etc. As described above, a standard format to render the“virtual ticket vouchers received” can be selected so that it matchesthe format of printed ticket vouchers that are received. Thus, in thedisplay resolution mode, the game controller 50 can be configured torender one or more virtual ticket vouchers in the “virtual ticketvoucher received stack” 60 on the fly using the code for rendering theimages of the virtual ticket vouchers and the virtual ticket voucherdata stored in stack 60.

As described above, the format of the data associated with the virtualticket vouchers and printed ticket vouchers can be the same. Anadvantage of using the same format is that the virtual ticket voucherscan be compatible with an existing cashless system providing redemptionand issuance of printed ticket vouchers. The difference being that theelectronic data for the virtual ticket vouchers remains in electronicform while the electronic data for the printed ticket vouchers is sentto a printer and added to a printed ticket. In the case of the receivedticket vouchers, the data for the virtual ticket voucher is receivedelectronically while printed ticket voucher data is read by some device(for instance, a bar-code scanner can read a bar code printed on theticket, which can be used to reference ticket information stored aremote server). After data is read from the printed ticket voucher andthe printed ticket voucher is redeemed, the received printed ticketvoucher can stored to a bill voucher/stack, such as 54. Typically, thebill/voucher stack 54 is in a cash box secured within a main cabinet ofthe EGM 2.

In one embodiment, the game controller 50 can maintain a ticket voucherreceived stack, which includes ticket voucher data for ticket vouchersreceived in a virtual ticket format or received in a printed ticketformat. The time at which each of the tickets is received can be storedin the stack so that the ticket voucher data can be retrieved in a timesequential order. In dispute resolution mode, the ticket voucher datafor the printed ticket vouchers can be retrieved and rendered in thesame way that virtual ticket voucher data is retrieved and rendered. Thevirtual ticket vouchers and the printed ticket vouchers can be renderedslightly differently, such as different color, to allow the format inwhich each type of ticket vouchers was received to be distinguished.

The issued virtual ticket voucher issued stack 61 can be maintained andaccessed in the manner similar to the virtual ticket voucher issuedstack 60. For instance, images of issued virtual ticket vouchers thathave been rendered can be saved to memory or the virtual ticket voucherdata of the issued vouchers can be saved to memory and later used torender images of virtual ticket vouchers that can be output to a displaydevice. In one embodiment, an electronic ticket voucher issued stack canbe maintained. The electronic ticket voucher issued stack can includeticket voucher data for ticket vouchers issued in a printed ticketvoucher format or a virtual ticket voucher format. The game controller50 can be configured to retrieve the ticket voucher data from the stackand render images of virtual ticket vouchers or printed ticket vouchersusing the data. The rendered ticket voucher images can be output to adisplay device.

Retrofit

Next, with respect to FIGS. 3A and 3B, a number of retrofit embodimentsare discussed. In the retrofit embodiments, a retrofit device can becoupled to an existing EGM 2 that doesn't provide virtual ticket voucherfunctionality to allow it to perform virtual ticket functions. In oneembodiment, as described with respect to FIG. 3A, the retrofit devicecan be configured so that software on the game controller, a ticketprinter and/or a bill/ticket acceptor doesn't need to be modified toallow virtual ticket voucher functionality to be provided. In thisembodiment, the game controller, ticket printer and bill/ticket acceptorcan communicate with one another as if the retrofit device is notpresent. Essentially, the retrofit device is invisible the devices inthat each of the devices is unaware of the functions that the retrofitdevice is performing.

In another embodiment, as described with respect to FIG. 3B, a device onthe EGM, such as a card reader, player tracking unit, ticket printerand/or bill/ticket acceptor, can be replaced with a substitute devicethat performs all or a portion of the virtual ticket vouchers functions.As an example, an existing printer that generates only printed ticketvouchers can be replaced with a printer that is configured to printticket vouchers or issue virtual ticket vouchers. In another example, anexisting bill/ticket acceptor can be replaced with a new bill/ticketacceptor that is configured to receive bills, printed ticket vouchersand virtual ticket vouchers.

As described above, a printer and/or bill validator can be configuredwith virtual ticket functions where the game controller is aware of thefunctionality. For instance, the game controller can be configured tocommand the printer to print a virtual ticket voucher to issue a virtualticket voucher and expect an acknowledgement that the virtual ticketvoucher has been issued from the printer. For a retrofit of an EGM wherethe game controller was designed without virtual ticket voucherfunctionality, the game controller may not have the capability to issuecommands associated with virtual ticket vouchers or receive and parseacknowledgements associated with virtual ticket vouchers from asecondary device, such as a printer with virtual ticket voucherfunctionality. Thus, as is described in more detail below, theinteractions between a retrofit device and a game controller, such as aretrofit printer with virtual ticket voucher functionality, can bedifferent than in the instance of a printer with virtual ticket voucherfunctionality where the game controller is configured to utilize thevirtual ticket functionality.

FIG. 3A is a block diagram of an electronic gaming machine 2 including aretrofit device 52 for providing virtual ticket-in and ticket-outservices. The retrofit device 52 can be configured and installed suchthat the game controller 50, the printer 38 and the billvalidator/acceptor do not require software modifications. The retrofitdevice 52 can be configured to perform virtual voucher processing 74 andprovide the wireless interface control 72 as described with aboverespect to FIGS. 1 and 2.

The retrofit device 52 can be configured to accept virtual ticketvouchers, issue virtual ticket vouchers or combinations thereof.Further, it can be configured to maintain soft meters, such as thev-ticket-in meter 80 and the v-ticket-out meter 82 and other meters asdescribed above. Thus, the retrofit device 52 can include a processorand memory for updating the software meters and a non-volatile memoryfor storing the soft meter values. The retrofit device 52 can beconfigured to report soft meter values to a remote device via a wired orwire communication interface associated with the retrofit device 52 oravailable on the EGM 2. Like the soft meters maintained in the gamecontroller 50, the soft meters maintained by the retrofit device can beconfigured to be generally non-resettable. However, the retrofit device52 can be configured to reset the soft meters after approval is receivedfrom a gaming regulator. For instance, the reset of the soft meters onthe retrofit device 52 can be performed in the presence of a gamingregulator.

The retrofit device 52 can be configured to update a set of hard meters86 separate from the hard meters 84 maintained by the game controller50. For instance, the retrofit device 52 can be configured to updatehard meter equivalents for one or more of the soft meters it maintains.In particular components, the hard meters can be integrated into theretrofit device 52. Like the embodiment described in FIG. 2, theretrofit device 52 can be configured to maintain a v-ticket voucherreceived stack 60 and a v-ticket voucher issued stack 61.

Further, as is described in more detail below, the retrofit device 52can be configured with device emulation 77. The device emulation 77 canallow the retrofit device 52 to respond to game controller 50 as if itwere another device on the EGM 2, such as the printer 38 and/or the billvalidator 22. The user interface provided on the retrofit device can bedifferent from either of the devices it is emulating. For instance,retrofit device that emulates a printer 38 and/or the bill validator maynot include a slot for issuing ticket voucher or a slot for acceptingticket vouchers. Further, the retrofit device can include additionalinterface devices, such as a display, touch screen, graphical userinterface, engraved or printed instructions or buttons, that aren'tfound on a typical bill validator or printer.

Next some details of the operation of the retrofit device are described.The E-cash in button and the E-cash out button 26 can be locatedsomewhere on the player interface. For instance, an existing playerinput panel can be replaced with a retrofit player input panel thatincludes the E-cash in button 24 and the E-cash out button 26. In otherembodiments, existing buttons on a player interface panel can bereprogrammed to provide these functions. In addition, the retrofitplayer input panel can include the wireless interface 18 and an expose aportion of the status indicator 19.

When the retrofit device 52 detects the E-cash in button 24 has beenactuated, it can place itself in a state where it is ready to receiveinformation associated with a virtual ticket voucher. For instance, itcan activate wireless interface 18 so that it is ready to receivevirtual ticket information from a portable electronic device and changea state of the status indicator 19 to indicate it is ready. If thestatus indicator includes a display than a message can be output to thedisplay indicating the retrofit device is ready to receive virtualticket voucher information. If the wireless interface is only leftactive for some time period, then the retrofit device 52 can initiate acountdown as was described above with respect to the EGM 2 to determinewhen to deactivate the wireless interface.

After the retrofit device 52 receives or recognizes the virtual ticketvoucher information, the retrofit device, via the device emulation 77,can respond to the game controller 50 as if it were bill validator 22that has accepted a printed ticket voucher. Towards this end, theretrofit device communications can be interposed on the communicationlink between the bill validator 22 and the game controller 50.Interposing the retrofit device on this communication link can involveinserting an adapter at one of the communication endpoints (i.e., at thebill validator or the game controller end) that routes thecommunications between the bill validator 22 and the game controllerthrough the retrofit device.

When the retrofit device is activated to receive a virtual ticketvoucher, such as after an actuation of the E-cash in button 24 isdetected, it can notify the game controller in the same way as the billvalidator 22 notifies the game controller 50 when a printed ticket hasbeen detected as being inserted. After the virtual ticket voucherinformation is received, the retrofit device 52 can notify the gamecontroller 50 on the bill validator communication link in the samemanner as if information has been read from a printed ticket voucher.During this process, commands/acknowledgements sent from the gamecontroller 50 to the bill validator 22 can be blocked from reaching thebill validator and instead can be processed and responded to by theretrofit device 52. If the virtual ticket voucher is validated, the gamecontroller 50 will update its soft meters and hard meters as if aprinted ticket voucher of some amount had been received by the billvalidator. As described above, in a non-retrofit embodiment, the gamecontroller 50 can be configured to update hard and/or soft metersassociated with virtual ticket vouchers, such as a number of virtualticket vouchers accepted and a value of the virtual ticket vouchersaccepted.

If the virtual ticket voucher information is not validated and the gamecontroller 50 sends a command to the bill acceptor 22 to reject aprinted ticket (send it back out the ticket slot), then, the retrofitdevice 52 can receive the command and respond to the game controller 50as if it has rejected a printed ticket. In one embodiment, the retrofitdevice 52 may have access to an interface, such as a display, thatallows it to display a message that indicates the virtual ticket voucheris invalid. In another embodiment, the retrofit device 52 can beconfigured to change a state of the status indicator 19 to indicate therejection of virtual ticket voucher. For instance, if so equipped, alight associated with the status indicator can flash red when thevirtual ticket voucher is not accepted. In a bill validator, a physicalejection of the printed ticket voucher is used to indicate the printedticket voucher has been ejected. In addition or alternatively, arejection message or rejection indication can sent to a portableelectronic device and the message or some indicator that the ticketvoucher has been rejected can be output to the portable electronicdevice.

If the retrofit device 52 detects that the bill validator is initiatinga transaction, such as when it has received a printed ticket voucher ora bill, it can allow communications between the game controller 50 andbill validator 22 to pass through. If the retrofit device 52 detects anactuation of the E-cash in button 24 before the transaction between thebill validator 22 and the game controller 50 is completed, the retrofitdevice 52 can be configured to ignore and not respond to the signal orthe retrofit device 52 can be configured to wait to respond to thesignal until it determines the transaction between the bill validator 22and the game controller 50 is completed. For instance, a state of thewireless interface 18 and it associated status indicator 19 may not bechanged until the transaction between the game controller 50 and thebill validator is completed. This sequence can occur if a user wishes todeposit credits via a printed ticket voucher and then deposit creditsvia a virtual ticket voucher.

Next, cash out transactions are described using the retrofit device 52.The E-cash out button 26 can be coupled to the retrofit device 52 andthe game controller 50 via the communication path for the cash outbutton 30. Thus, when either the E-cash out button 26 or the cash outbutton 30 is actuated, the game controller can receive and process thesignal as if the cash out button 30 has been actuated, i.e., the gamecontroller 50 is not configured to distinguish that the signal wasgenerated from the E-cash out button 26 or the cash out button 30. Then,when a signal is received from either button, the game controller 50 canrespond in the same manner as if the cash out button has been activated.The game controller 50 can contact the validation server to receiveticket voucher information, such as a unique validation number for theticket voucher that is to be issued. Then, the game controller 50 cangenerate and send instructions to the printer 38 to print a ticketvoucher including the unique validation number.

The retrofit device 52 can be interposed on the communication pathbetween the printer 38 and the game controller 50, such as in the mannerdescribed with respect to the bill validator. The retrofit device can beembodied physically as a separate device or logically within an existingdevice. The retrofit device 52 can receive the print instructions,activate the wireless interface 18 and change the status indicator 19.If a portable electronic device is detected and the virtual ticketvoucher is transferred to the portable electronic device within sometime period, the retrofit device 52 can respond to the game controller50 as if it were the printer 38 and it had issued a printed ticket. Ifthe retrofit device 52 doesn't issue the virtual ticket voucher withinthe time period, it can change the status of the wireless interface 18and the status indicator 19 and release the initial print command to theprinter 38 so that transaction is now processed as printed ticket. Itcan then allow subsequent communications between the printer 38 and thegame controller 50 to pass through the retrofit device 52 so that theprinted ticket voucher transaction can be completed.

When the retrofit device 52 receives a print voucher command from thegame controller 50 and an actuation of the E-cash out button hasn't beendetected, then the retrofit device 52 can be configured to allowcommunications between the game controller 50 and the printer 38 to passthrough the retrofit device 52 until the printed ticket transaction iscomplete. In this example, the print voucher command can be initiatedwhen a signal from an actuation of a cash-out button on the EGM 2 isdetected. If the retrofit device detects an actuation of the E-cash outbutton 26 after the cash-out transaction has been initiated via thecash-out button, then the retrofit device 52 can be configured to ignorethe E-cash out button because a printed voucher transaction has alreadybeen initiated. In alternate embodiments, the printer 38 and/or the billvalidator can be removed from the EGM 2. In these embodiments, theretrofit device 52 can be configured to emulate the printer 38 and/orthe bill validator to issue and/or receive only virtual ticket vouchers.

In one embodiment, the retrofit device 52 can be configured to reportits virtual ticket voucher activity to a remote device, such as thevalidation server 68 or the accounting server 70. For instance, theretrofit device 68 can be configured to communicate which of the printedticket voucher transactions initiated by the game controller 50 wereactually completed as virtual ticket voucher transactions. Similarly,the retrofit device 52 can be configured to communicate to a remotedevice which ones of the redeemed ticket vouchers reported as beingreceived in the bill validator 22 by the game controller 50 wereactually virtual ticket vouchers. Similarly, if the retrofit device 52is configured to accept virtual currency, such as via an e-walletapplication, the retrofit device 52 can be configured to communicate toa remote device when virtual currency is accepted. This informationwould be useful for the soft count process since the virtual ticketvouchers or the virtual currency won't be in the cash box when the billsand printed tickets in the cash box are counted.

The retrofit device 52 can communicate with a remote device via the gamecontroller 50 and the network interface 56 if the game controller 50 isconfigured to allow pass through communications from a device, such as52. In another example, the retrofit device can be directly coupled tothe network interface 56 if the network interface 56 allows for suchcommunications and initiate communications through the network interface56. In yet another embodiment, the retrofit device 52 can include itsown communication interface, such as wireless communication interface,that allows it communicate with server 68 or 70 via some othercommunication pathway.

In FIG. 3A, the retrofit device 52 is shown as a separate device. Inother embodiments, the functions of the retrofit device can beintegrated into an existing device on the EGM 2. For instance, a cardreader can be configured to perform the functions of the retrofit device52. The card reader retrofit device can be configured performcommunications in the manner described for the retrofit device 52. Forinstance, it can be interposed between the communication connectionsbetween the printer and the game controller and/or between the billvalidator and the game controller. In addition, it can be configured toperform card reader functions. In particular embodiments, a wirelessinterface 18 and status indicator 19 can be provided near the cardreader slot that allows access to the interior of the card reader suchthat the status indicator is visible to the player. In addition, anE-cash out button, such as 26 and an E-cash in button 24, can beprovided near the card reader slot. The interface on the card readerincluding the status indicator, E-cash-in and E-cash out buttons andwireless interface can be arranged such the card reader can fit in anexisting card reader slot associated with the EGM 2.

In another embodiment, the functions of the retrofit device can beincorporated into a player tracking unit. If desired, the wirelessinterface 18, the status indicator, the E-cash in button and/or theE-cash out button can be integrated into the player tracking interface.The cabinet of the EGM 2 includes an aperture that can be filled by theplayer tracking interface so that the features of the player trackinginterface are accessible to a player. This feature can allow the playertracking unit with virtual ticket voucher in and virtual ticket voucherout capabilities to replace and fit in the space occupied by an existingplayer tracking unit without these capabilities.

As another example, the printer 38 or the bill validator 22 can beconfigured with the retrofit device functions. If the printer 38 isincorporated with all of the retrofit device functions, then the printer38 can be configured to determine whether a ticket voucher is to beissued as virtual ticket voucher or a printed ticket voucher but respondto the game controller 50 as if all of the transactions were printedticket vouchers. Thus, the existing connection between the gamecontroller 50 and printer 38 may not have to be modified. However, toperform virtual ticket-in functions, the printer 38 can be interposedbetween the communication channel between the game controller 50 and thebill validator. As described above for the retrofit device, the printer38 can be configured to block certain communications to the billvalidator 22 and in some instances respond to the gaming controller 50as if it were a bill validator.

In yet another example, if the bill validator 22 is incorporated withall of the retrofit device functions, then the bill validator can beconfigured to determine whether an accepted ticket voucher is a virtualticket voucher or a printed ticket voucher but respond to the gamecontroller 50 as if all of the transactions were printed ticketvouchers. The existing connection between the game controller 50 andbill validator may not have to be modified. However, to perform virtualticket out functions, the bill validator can be interposed between thecommunication channel between the game controller 50 and the printer 38.As described above for the retrofit device, the bill validator can beconfigured to block certain communications to the printer 22 and in someinstances respond to the gaming controller 50 as if it were a printer.

In yet other embodiments, the E-cash in button 24 and/or the E-cash outbutton 26 functions can be embodied on a portable electronic device. Asan example, the EGM 2 can be configured to establish communications withthe portable electronic device. After communications are establishedwith the portable electronic device, an application executing on theportable electronic device can generate a touch screen button toinitiate an E-cash in transaction or an E-cash out transaction. Whenportable electronic device detects one of the buttons has been selected,a message requesting the EGM 2 to initiate an E-cash in transaction oran E-cash out transaction can be sent to the EGM 2. The message can bereceived by the game controller or another device with a secondarycontroller, such as a player tracking unit, bill validator, printer orcard reader, configured to respond to the message. In response toreceiving the message and E-cash in transaction and/or an E-cash outtransaction can be generated.

Thus, in particular embodiments, the EGM 2 may or may not include theE-cash in button 24 or the E-cash out button 26. In addition, the EGM 2can include E-cash in button 24 and/or an E-cash out button 26 and canalso be configured to receive a message from a portable electronicdevice requesting an E-cash in transaction or an E-cash out transaction.In this embodiment, the EGM 2 can initiate the E-cash in transaction inresponse to an actuation of the E-cash in button 24 or in response toreceiving a message from a portable electronic device or some otherremote device requesting the E-cash in transaction. Similarly, the EGM 2can initiate the E-cash out transaction in response to an actuation ofthe E-cash out button 26 or in response to receiving a message from aportable electronic device or some other remote device requesting theE-cash out transaction.

In one embodiment, the remote device requesting the E-cash in or E-cashout transaction can be a remote server. The remote server can open up a“service window” on the EGM 2 that includes a touch screen button toinitiate an E-cash in transaction or an E-cash out transaction. Theremote server can receive an indication that the E-cash in button or theE-cash out button has been selected. In response, the remote server cansend a message to the EGM 2 requesting an E-cash in transaction or anE-cash out transaction. In response, the gaming controller or asecondary controller on the EGM 2 that receives the request message caninitiate the E-cash in transaction or the E-cash out transactioninvolving a portable electronic device.

Next embodiments are described where some of the retrofit devicefunctions are split between secondary devices on an EGM, such as a billvalidator and a printer. FIG. 3B is a block diagram of an electronicgaming machine including a bill acceptor and a printer for providingvirtual ticket-in and ticket-out services. In FIG. 3B, although thevirtual ticket functions are shown split between a bill validator andprinter other combinations are possible. For instance, the virtualticket functions can be split between a card reader and a playertracking unit or between a card reader and a printer. In addition, thefunctions allocated to each device can be different. For instance, inFIG. 3B, the printer 38 is described as handling virtual ticket outfunctions while the bill validator is shown as handling virtual ticketin functions. In alternate embodiments, these functions can be reversedbetween the devices. Thus, the example described with respect to FIG. 3Bis provided for illustrated purposes and is not meant to be limiting.

In FIG. 3B, the bill validator 108 is configured to handle virtualticket in functions. Thus, it can be configured to perform theprocessing associated with receiving virtual ticket vouchers. Theprocessing can include maintaining and/or updating hard and soft meters.If the cash box includes a memory for storing records for receivedvirtual ticket vouchers, then the bill validator 108 can be configuredto update the memory with virtual ticket voucher information that isreceived.

In FIG. 3B, the bill validator 108 is configured as a retrofit device.Thus, the bill validator can be configured to report virtual ticketvoucher transactions to the game controller 50 as a printed ticketvoucher transaction. In one embodiment, the bill validator 108 caninclude communication capabilities, such as output interface 104 thatallows the device to communicate virtual ticket voucher information to aremote device, such as server 68. In addition, the bill validator 108can include an operator mode 105 that allows the bill validator to beinterrogated for information, such as for its soft meter valuesassociated with the virtual ticket vouchers. In one embodiment, via theoutput interface 104, this information can be displayed to a remotedevice, such as portable electronic device carried by an operator or toa display device coupled to the EGM 2. In a non-retrofit embodiment,this information can be reported to the game controller 50 andmaintained as soft meters by the game controller 50. Thus, the operatormode 105 for displaying soft meter values may not be needed with anon-retrofit device but could be included as a back-up to the gamecontroller 50 in some embodiments.

In one embodiment, the bill validator 108 can include one or more of awireless interface 106, a status indicator (not shown) and the E-cash inbutton 24, built into the face of the bill validator including the slotfor receiving bills. Alternatively, the bill validator 108 can beconfigured to receive a message from a portable electronic device or aremote server requesting an E-cash in transaction and may not include anE-cash in button 24. In this embodiment, the bill validator 108 canestablish a communication session with the portable electronic deviceand/or a remote server and then receive the message requesting theE-cash in transaction from one of the devices.

The bill validator 108 can be configured to activate the wirelessinterface 106 and process information received via the wirelessinterface. Further, it can be configured to control the status indicatorto indicate changes in state of the wireless interface 106, such as ifthe wireless interface is turned on or off. In a non-retrofitembodiment, when the E-cash in button 24 is included on the billvalidator and it is actuated, the bill validator 108 can be configuredto report the initiation of virtual ticket in transaction to the gamecontroller rather than reporting it as a printed ticket-in transaction.

In FIG. 3B, the printer 102 is configured to handle virtual ticket outfunctions. Thus, it can be configured to perform the processingassociated with issuing virtual ticket vouchers. The processing caninclude maintaining and/or updating hard and soft meters associated withthe virtual ticket in functions. In FIG. 3B, the printer 102 isconfigured as a retrofit device. Thus, the printer 102 can be configuredto report virtual ticket voucher transactions to the game controller 50as printed ticket voucher transactions. However, the printer 102 caninclude communication capabilities, such as output interface 92 thatallows the device to communicate virtual ticket voucher information to aremote device, such as server 68.

The printer 102 can include an operator mode 91 that allows the printer102 to be interrogated for information, such as for its soft metervalues associated with the virtual ticket vouchers that have beenissued. As described above, the printer can include a non-volatilememory for maintaining the soft meters, such as battery-backed RAM,Flash or NV-RAM technologies. In one embodiment, via the outputinterface 92, this information can be displayed to a remote device, suchas portable electronic device carried by an operator or to a displaydevice coupled to the EGM 2. In a non-retrofit embodiment, thisinformation can be reported to the game controller 50 and maintained assoft meters by the game controller 50. Thus, the operator mode 91 fordisplaying soft meter values may not be needed with a non-retrofitprinter device but could be included as a back-up to the game controller50.

In yet another embodiment, the printer 102 can include one or more of awireless interface 91, a status indicator (not shown) and the E-cash outbutton 26, built into the face of the printer 102 including the slot forejecting tickets that forms a portion of the EGM exterior. The printercan be configured to activate the wireless interface 90 and processinformation received via the wireless interface. Further, it can beconfigured to control the status indicator to indicate changes in stateof the wireless interface 90, such as if the wireless interface isturned on or off. As described above, if the E-cash out button isincluded in the printer interface then the printer can be coupled to thecommunication channel associated with the cash out button, such that acash-out signal is sent to the controller 50. The printer 102 can beconfigured to generate this signal. In response, the controller 50 caninitiate a cash-out sequence where it is responding as if a printedticket voucher is being generated. In non-retrofit embodiments where thecontroller 50 includes virtual ticket out functionality, the printer 102can notify the game controller 50 that the E-cash out button 26 has beenactuated and in response the game controller 50 can initiate and E-cashout transaction.

In the example described above, the bill validator 108 and the printer102 each include separate wireless interfaces. If a NFC compatibleinterface was used, then as part of a virtual ticket in transaction, aportable electronic device might need to be placed near or in contactwith the bill validator interface. In addition, as part of a virtualticket out transaction, the portable electronic device might need to beplaced near or in contact with the printer interface. Having to placethe portable electronic device in different locations for each type oftransaction reduces the required interfaces, thus, in one embodiment,two devices, such as a printer and a bill validator with virtual ticketout and ticket in capabilities can share a wireless interface and statusindicator. However, it may be more intuitive for a user to place theirdevice near a cash-in device for a cash-in transaction and near acash-out device for a cash-out transaction. Thus, in some embodiments,separate wireless interfaces may be maintained.

In this embodiment, provisions may need to be made in regards to sharingcontrol of the interface and status indicator. For instance, thewireless interface can communicate its status, i.e., whether it is inuse or not. The bill validator and printer can be configured to respondto the case where the interface is being utilized by the other deviceand it wishes to initiate a transaction. For instance, after a virtualticket out transaction is initiated on the printer 102, the printermight start controlling the shared interface. If the E-cash in buttonwas pressed, the bill validator can attempt to control the interface butreceive an indication from the wireless interface that it is busy. Inresponse to the bill validator receiving an indication that wirelessinterface is busy, the bill validator can be configured to ignore thevirtual ticket in request. In another example, it can be configured tohold the transaction in abeyance and continue to check the status of thewireless interface. When it detects the status of the wireless interfaceis inactive (i.e., the printer is not controlling the interface), it caninitiate the virtual ticket in transaction on the wireless interface.

In other embodiments, only one of the devices and its associatedfunctions can be included. For instance, an EGM can be configured with aretrofit printer device that can issue virtual ticket vouchers orprinted ticket vouchers but is only able to accept printed ticketvouchers and thus, doesn't include a bill validator with the functionsdescribed above. In another example, the EGM can be configured with aretrofit bill validator that can receive virtual ticket vouchers orprinted ticket vouchers but is only able to issue printed ticketvouchers and thus, doesn't include a printer with the functionsdescribed above.

Virtual Ticket Management

With respect to the FIGS. 4A-4C, the management of virtual tickets on aportable electronic device is described. The management can includeinteractions with a remote server that allow virtual tickets stored onthe portable electronic device to be redeemed or new virtual ticketvouchers to be created as well as other virtual ticket services to beprovided. FIG. 4A shows a block diagram of a system providing remotecreation, validation and redemption of virtual tickets in accordancewith the described embodiments. In one embodiment, the system includes aserver 200 configured to communicate with remote devices, such asportable electronic device 202, via a WAN 225, such as the Internet.

The portable electronic device 202 can include a processor, a memory anda network interface 220. In addition, the portable electronic device caninclude a number of I/O interfaces 222. The I/O interfaces 222 caninclude visual and audio interfaces, such as displays, speakers,cameras, microphones, a touchscreen and an audio jack. The I/Ointerfaces 222 allow a user to interact with the portable electronicdevice including receiving video images and audio content associatedwith different applications executed on the portable electronic device.Further, the I/O interfaces 222 can include wired and/or wirelessinterfaces that allow the portable electronic device to communicate withother devices directly or via a network connection. Further, theportable electronic device 202 can include various a GPS receivers andvarious sensors, such as an accelerometer. The GPS receiver can be usedfor applications requiring a location. The accelerometer can be used todetect a movement of the device, which in some instances can used togenerate control commands. As an example, the portable electronic device202 can be a smartphone or a tablet computer, such as an iPhone™ or aniPad™ by Apple™.

As described above, the portable electronic device 202 can be used withvirtual ticket vouchers. In particular, a virtual ticket voucher storedon the portable electronic device 202 can be transmitted to an EGM andvalidated to allow credit associated with the virtual ticket voucher tobe deposited on the EGM. Also, a virtual ticket voucher generated by anEGM can be transmitted to the portable electronic device 202 to allowcash or credits to be transferred from the EGM to the portableelectronic device. The virtual ticket voucher received by the portableelectronic device from the EGM can later be used for game play on otherEGMs, can be redeemed for cash at a cashier station or at a redemptionkiosk, or can be converted into a virtual cash form compatible with anE-Wallet application.

In one embodiment, the portable electronic device 202 can be configuredto execute a voucher management application 218 for managing virtualticket vouchers. The voucher management application 218 can bedownloaded from a remote device, such as server 200. A vouchermanagement download application 215 on server 200 can be configured todownload voucher management applications compatible with differentoperating systems, such as iOS™ by Apple™, Android™ by Google™, Windows7 by Microsoft™ or QNX RTOS by RIM™. The different operating systems canbe utilized by different types of portable electronic devices.

In other embodiments, the portable electronic device 202 can beimplemented more simply. For instance, a smart card or an appropriatelyconfigured memory stick can be used to send virtual ticket vouchers toan EGM and receive virtual ticket vouchers from the EGM. For instance, awired or wireless interface can be provided on the EGM to communicatewith the memory stick. The EGM can detect the memory stick and displayits contents related to virtual ticket vouchers to a display. On thedisplay, such as a touch screen display, the user may be able to dragvirtual ticket vouchers to a particular area associated with the EGM,such as a box rendered on the display, to redeem the vouchers and dragvirtual ticket vouchers from an area associated with the EGM to an areaassociated with the memory stick to store the virtual ticket voucher tothe memory stick.

The virtual ticket voucher management application can be configured tostore virtual ticket voucher information 212 associated with unredeemedand redeemed virtual ticket vouchers. In one embodiment, the application218 can be configured to manage account data associated with a loyaltyprogram. Further, the application 218 can include voucher templates 214that allow a user to customize the appearance of a virtual ticketvoucher displayed on the portable electronic device 202. For instance,as described above, a virtual ticket voucher can be rendered in theformat of a printed ticket voucher where via the voucher templates 214,the user can customize the rendered appearance of virtual ticketvouchers stored on the portable electronic device 202. In oneembodiment, the ticket customization templates can be downloaded from aremote host, such as web-site affiliated with a casino or a gamingmachine manufacturer.

In addition, the application 218 can provide a voucher interface 216.The voucher interface 216 can be configured to allow a user to organize,display and redeem their virtual ticket vouchers and manage loyaltyprogram information. A few examples of an interface associated with thevirtual ticket voucher management application are described with respectto FIGS. 4B and 4C. In one embodiment, the voucher managementapplication can be configured to determine an expiration date associatedwith a virtual ticket voucher stored on the portable electronic device.When a virtual ticket voucher is near its expiration date, the interface216 can be configured to send a notification message to the user, suchas an alert message. An expiration policy for virtual ticket vouchersmay vary from casino to casino. Thus, the application 218 can beconfigured to identify an establishment from which the virtual voucherwas received and determine the expiration data for the virtual ticketvoucher based upon the expiration policy associated with theestablishment. In some instance, the expiration policy associated withvirtual ticket voucher can be included in the virtual ticket voucherinformation that is received when a virtual ticket voucher istransferred to the portable electronic device. Thus, the application 218can be configured to use this information in determining whether avirtual ticket voucher is about to expire.

In other embodiments, the virtual ticket management application 218 canbe configured to communicate with a remote device, such as server 200,to receive other additional virtual ticket voucher services. Forinstance, server 200 can be configured to provide downloads includingupdates of the voucher management application 218 to remote devices,such as device 200. In one embodiment, the server 200 can include logic208 that allows a virtual ticket voucher to be issued and transmitted toa portable electronic device 202. To perform this transaction, theserver 200 can be configured to 1) contact a validation server that isutilized by one or more casino locations to receive unique voucherinformation, 2) construct a valid virtual ticket voucher, 3) confirmpayment for the virtual ticket voucher, 4) transmit the virtual ticketvoucher to the portable electronic device and 5) notify the validationserver that the virtual ticket voucher has been issued. In addition, theserver 200 can be configured to send device information associated withthe portable electronic device 202, such as unique device information.In one embodiment, as described above, the validation server may requirethe unique device information to validate the virtual ticket voucher.

A restriction with the virtual ticket voucher issued by server 200 canbe that the virtual ticket voucher has to be redeemed at the casino forwhich is valid. As will be described in more detail as follows, theserver 200 can be configured to redeem the virtual ticket vouchersissued at a gaming property, such as a casino. In one embodiment, theserver 200 may not validate tickets issued from the server 200. Anotherrestriction can be the server 200 may not issue virtual tickets above acertain value, such as above $100 dollars.

Another type of virtual ticket voucher that can be purchased is avirtual ticket voucher redeemable for promotional credits. Promotionalcredits can be played on an EGM but can't be redeemed for cash. However,awards earned from wagers using the promotional credits can be redeemedfor cash. As an example, the server 200 can be configured to allow apurchase $100 dollars worth of promotional credits for $50 dollars. Thistype of offer can offered in a group fashion, such as purchase $100dollars worth of promotional credits for $50 if 50 people sign-up forthe deal. The purchase of the promotional credits can be handled by thepromotion application 204. To allow redemption of promotional credits,the server 200 can be configured to contact a validation server at agaming property to receive a unique validation number that allows thepromotional credits to be redeemed at the gaming property.

The server 200 can provide incentives to purchase a virtual ticketvoucher that can redeemed for cash at a casino. For instance, asdescribed in the previous paragraph, if a cash value virtual ticketvouchers is purchase for a certain value, the server 200 can beconfigured to issue a second virtual ticket voucher for promotionalcredits. As other incentives, the server 200 can be configured to issuevirtual ticket vouchers that can be redeemed for discounts for servicesat a casino property, such as a discount at restaurant, a discount at aspa, a discount at a gaming property store or a discount on lodging. Theamount of incentives provided with a purchase of virtual ticket vouchercan be related to the value of the virtual ticket voucher purchased. Inone embodiment, to receive a virtual ticket voucher redeemable for anincentive, such as a discount for lodging, a user may have to provideidentification information. When identification information is provided,the redemption of the virtual ticket voucher redeemable for an incentivemay be limited to a particular person associated with the identificationinformation. The server 200 can store a record of the identificationinformation associated with each virtual ticket voucher.

In other embodiments, the server 200 can be configured to providevirtual ticket voucher redemption 206. The server 200 can be configuredto establish contact with a remote device, such as portable electronicdevice 202 and receive virtual ticket voucher information associatedwith a virtual ticket voucher stored on the portable electronic devicethat was transferred to the portable electronic device at a gamingproperty. After receiving the virtual ticket voucher information fromthe portable electronic device, the server 200 can be configured tocontact a validation server 200 at the gaming property, transmit thevirtual ticket voucher information and receive a confirmation in regardsto whether the virtual ticket voucher is valid and hasn't beenpreviously redeemed.

If the virtual ticket voucher is validated, then server 200 can beconfigured to provide the redemption value of the virtual ticket voucherto a user and notify a validation server that the virtual ticket voucherhas been redeemed. For instance, the server 200 can be configured tomail a check for the value of the virtual ticket. In another embodiment,the server can be configured to make an electronic funds transfer to anaccount specified by a user, such as PayPal™ account, a regular bankaccount or some other account accessible to the user.

In another embodiment, the user can have an account on server 200 wherevirtual ticket vouchers can be stored. The account can be set up toautomatically redeem and transfer funds associated with the redeemedvirtual ticket vouchers to a user's bank account. For instance, theaccount can be set-up to perform this action automatically 30 days aftera virtual ticket voucher has been issued. In another embodiment, avoucher management application executed on a user's mobile device or ahome computer can be configured to carry out this process (e.g., contactthe server 200, request a redemption of a virtual ticket voucher and atransfer of funds to a user's bank account when the ticket is valid).

To encourage user's to redeem their virtual ticket vouchers at thegaming property where they were issued, limits can be set on when avirtual ticket voucher can be redeemed. For instance, on server 200, avirtual ticket voucher may not redeemable until it is close to itsexpiration date, such as week from expiring. Thus, a user would have towait unit the virtual ticket voucher was about to expire to redeemon-line or else travel to the gaming property where it was issued tohave it redeemed. In another example, the server 200 may not beconfigured to redeem virtual ticket vouchers over a certain amount, suchas over $100 dollars.

In one embodiment, rather than redeeming virtual ticket vouchers, theserver 200 can be configured to provide an extension of the expirationdate. Thus, if a virtual ticket voucher was about to expire, via aportable electronic device, the user can send the virtual ticket voucherinformation to the server 200 and request and expiration date extension.In response, the server 200 can contact a validation server at a gamingproperty and request an extension. If granted, the validation server cantransmit the new expiration date to the server 200 and then the server200 can notify the user associated with the portable electronic device202 of the new expiration date.

Next, a few details of a voucher management application executable on aportable electronic device, such as 202, are discussed. FIGS. 4B and 4Cshow block diagrams of an application for managing virtual tickets on aportable electronic device. In particular, FIGS. 4B and 4C show examplesof interface output data, 230 and 232, associated with the vouchermanagement application that can be output to the display of a portableelectronic device.

In one embodiment, the voucher management application can be configuredto display information associated with one or more virtual ticketvouchers. As previously described, the virtual ticket voucherinformation can be rendered in the format of printed ticket voucher. Inone embodiment, the virtual ticket voucher can be rendered in a formatthat is consistent with the gaming property from which it was issued. Inanother embodiment, voucher management application can be configuredwith options, such as voucher format templates, that allow a user tocustomize the appearance of the virtual ticket vouchers rendered on thedisplay of the portable electronic device. In some instances, all or aportion information can be transferred to a gaming device, such as anEGM. When virtual ticket voucher information is transferred to the EGM,the EGM can be configured to render an image of the virtual ticketvoucher on one of its displays using the user-selected format parametersfor the virtual ticket voucher.

If multiple virtual ticket vouchers are rendered on a display of theportable electronic device simultaneously, the size of each renderedvoucher may be reduced and information associated with the renderedvoucher may be difficult to see. Towards this end, the vouchermanagement application can be configured to render informationassociated with rendered voucher, such as value amount, in a largerformat than other information rendered in the image of the virtualticket voucher. This data can be rendered separately from the image ofthe virtual ticket voucher, such as below the virtual ticket voucher.Further, the information can be rendered as plain text, such as in aspread sheet format, without image data. The voucher managementapplication can include a feature that allows a user to select a formatfor displaying the data or can be configured to switch formats dependingon the amount of data that needs to be displayed.

In one embodiment, a bar-code or other optically formatted image data(e.g., QR code) rendered in an image of a virtual ticket voucher can beused to redeem a virtual ticket voucher. For instance, at a cashierstation a user can present their portable electronic device while it isdisplaying the bar-code. The cashier can scan the bar-code and theinformation can be sent to a remote server for validation purposes. Ifthe virtual ticket voucher is valid, then the cashier can provide thevalue associated with the virtual ticket voucher to the person thatpresented the portable electronic device.

In a particular embodiment, the voucher management application caninclude print capabilities that allow an image of virtual ticket voucherto be printed out via a standard printer. In some instances, electronicgaming machines or other redemption devices can be configured to acceptvirtual ticket vouchers printed in this manner. A user may wish to printout a record of a previously redeemed ticket. For instance, the user canprint out a ticket associated with a large payout as a souvenir. Ifdesired, a water mark or some other indication can be added to aredeemed ticket when it is printed to indicate it has already beenredeemed.

The voucher management application can be configured to manage virtualvouchers from multiple locations. The application can be configured togroup the vouchers according to location. As shown in FIG. 4B, fourvirtual ticket vouchers from casino “A” are displayed. The vouchermanagement application and a redemption device, such as an EGM or aredemption kiosk can be configured to allow multiple virtual ticketvouchers to be redeemed at once. For example, the user can select 3 orthe 4 virtual ticket vouchers in FIG. 4B and then initiate a redemptiontransaction with an EGM. The selected vouchers can be transmittedsimultaneously and the can be separately validated by the EGM. Each ofthe validated virtual ticket vouchers can be redeemed for credits on theEGM. The application can be configured to keep a record of each voucherredeemed including a value of the voucher, when it was redeemed andwhere it was redeemed. Images of the redeemed vouchers can be removedfrom the portable electronic device or can be organized separately fromthe virtual ticket vouchers that are still redeemable.

The voucher application can be configured to allow the user tooptionally share their loyalty program information during the virtualticket voucher transaction. For instance, if the user actuates the sharebutton, then their loyalty program information can be uploaded to aredemption device, such as an EGM, during the virtual ticket vouchertransaction. If the share button is not selected, then the virtualticket voucher transaction can occur anonymously.

In some instances, the redemption device, such as an EGM, can beconfigured to require secondary authentication of a virtual ticketvoucher. In another example, this feature can be built into the virtualvoucher management application. For instance, as shown in interface 232in FIG. 4C, the application can require the user to enter a 4-digit PINfor secondary authentication purposes. In another example, theapplication can require the user to enter a password. In yet anotherexample, the user can be required to correctly answer one or morechallenge questions.

In one embodiment, a second authentication may only be required fortransactions above a certain amount, such as $25 dollars. If multiplevirtual ticket vouchers are simultaneously redeemed, then the totalamount of the transaction based on the value of all of the virtualticket vouchers being redeemed during the transaction may have to beover a certain amount before secondary authentication is required. Anadvantage of requiring secondary authentication is that if the portableelectronic device is lost or stolen another person may not be able toredeem the virtual ticket vouchers. The voucher management applicationcan be configured to allow a user to back-up their virtual ticketvoucher information on another device controlled by the user or a remotestorage device in the “cloud.” Thus, using the back-up data, it may bepossible for the user to recover and redeem their virtual ticketvouchers if a portable electronic device storing the virtual ticketvouchers is lost or stolen.

In another embodiment, the voucher management application can beconfigured to convert a physically printed ticket voucher to a virtualticket voucher. For instance, on a device with a camera, an image can betaken of the printed ticket voucher. The application can be configuredto parse information from the printed ticket voucher to create a virtualticket voucher. Later, the virtual ticket voucher associated withprinted ticket voucher can be redeemed for cash or additional game playon a gaming device.

The user can save the printed ticket voucher if desired. If the printedticket voucher is redeemed before the virtual ticket voucher copy, thena later attempt to redeem the virtual ticket voucher copy will not workbecause the host system will already have a record that the ticketvoucher has been redeemed. If the virtual ticket voucher copy isredeemed before the printed ticket voucher, then a later attempt toredeem the printed ticket voucher will not work because the host systemwill already have a record that the ticket voucher is redeemed.

In particular embodiments, a gaming device can be configured to issueboth a printed ticket voucher and a virtual ticket voucher. The userreceiving the printed ticket voucher and the virtual ticket voucher(stored to a device) can then choose which format to use when redeemingthe ticket voucher. As an example, a retrofit device or a secondarydevice on an EGM, such as a card reader, player tracking unit, billvalidator or printer, can be configured to issue a virtual ticketvoucher when a printed ticket voucher is issued. Thus, the printedticket voucher can issue normally in response to a cash out request. Inaddition, the retrofit device or the secondary device can be configuredto issue a virtual ticket voucher and communicate the virtual ticketvoucher information to a user's portable electronic device.

In yet other embodiment, the voucher management application can beconfigured to receive an image of a check. Software exists that allowsan image of a check to be scanned or a user to take a picture of a checkthen have the check electronically deposited into a bank account. At aredemption station, rather than receiving cash for a redeemed virtualticket voucher or a printed ticket voucher, an electronic image orimages of a check that can be electronically deposited into a user'sbank account can be received via the voucher management application onthe user's device. Then, the check can be deposited into the user's bankaccount. This approach may be preferable to a user than receiving alarge amount of cash.

Methods for Managing Virtual Ticket Vouchers on an EGM

Next with respect to FIG. 5A methods of managing virtual ticket vouchersin an EGM are described. FIG. 5A is a method 300 in a gaming machine forredeeming virtual ticket vouchers. In 302, an actuation of an E-cash-inbutton can be detected. In one embodiment, the E-cash-in button can be amechanical or a touchscreen button. In another embodiment, a wirelesscommunication, such as a near-field communication, between a portableelectronic device and the EGM can be used to initiate the transaction.For instance, a user can wave their portable electronic device near awireless interface to initiate the E-Cash-in transaction. In response todetecting the request for the E-cash-in transaction, the EGM caninitiate a virtual voucher transaction. In one embodiment, the EGM canbe configured establish communications with a portable electronicdevice. After communications are established, via the application, theapplication the user can initiate a virtual ticket voucher transaction.Thus, a mechanical button or touch screen button on the EGM may not beneeded to initiate a virtual ticket voucher transaction.

In 304, in response, the EGM can initiate a virtual ticket voucherredemption transaction. In one embodiment, the EGM can be configured toactivate an interface, such as a wireless interface enabling wirelesscommunications and change the status of a status indicator to indicatethe wireless interface is ready to receive virtual ticket voucherinformation from a portable electronic device. Then, the EGM caninitiate a countdown timer. If the virtual ticket voucher informationassociated with the transaction within a specific time period, then theEGM can be configured to cancel the transaction. If a wireless interfaceand a status indicator are used, then the states of these devices can bechanged. For instance, the wireless interface can be turned off and thestate of the status indicator can be changed to indicate the wirelessinterface is inactive.

In particular embodiments, the wireless communications can be carriedout using a wireless protocol, such as NFC, Bluetooth™ or Wi-Fi™. In oneembodiment, a combination of wireless protocols can be used. Forinstance, an NFC communication can be used to set up a device pairingbetween the EGM and a portable electronic device that uses Bluetooth™ orWi-Fi™ compatible communications.

In another embodiment, a wireless interface and status interface may notbe used. Instead, via an application executing on a portable electronicdevice and a previously established communication connection between theEGM and the portable electronic device, the application can begin atransfer of virtual ticket voucher information to the EGM in response toreceiving a selection initiating the transfer of virtual ticket voucherinformation. The selection can be made on an interface associated withthe application that is generated on the portable electronic device. In306, the EGM can receive virtual ticket voucher information from theportable electronic device. If the EGM includes a NFC compatiblewireless interface and the portable electronic device is NFC enabled,then the portable electronic device has to be brought into range of theNFC compatible wireless interface, such as within 4 cm or less from theinterface to enable the transaction.

In one embodiment, in 308, the EGM can be configured to output a portionof the virtual ticket voucher information to the display. The output ofthe virtual ticket voucher information can provide an indication thatthe virtual ticket voucher information has been received by the EGM 2.In a particular embodiment, the EGM 2 can be configured to render animage of a ticket voucher to the display including all or a portion thevirtual ticket voucher information. The image can be rendered such thatthe image is similar in format to a printed ticket voucher. Theapplication executing on the portable electronic device can includeoptions, such as a number of ticket voucher templates, which allow auser to customize the appearance of virtual ticket vouchers rendered onthe portable electronic device. In one embodiment, some of the customappearance information selected by the user can be transferred from theportable electronic device to the EGM to affect an appearance of animage rendered and displayed on the EGM of the virtual ticket voucher.In another embodiment, the virtual ticket voucher appearance informationcan be retrieved from a loyalty program account when a user providesinformation, such a loyalty program account number. The informationretrieved from the loyalty program account can be used to modify theappearance of virtual ticket vouchers rendered on a display of the EGM.

In 310, the EGM can send virtual ticket voucher information to a remoteserver for validation purposes. In one embodiment, the virtual ticketvoucher information can include unique identification informationassociated with the portable electronic device. In 312, the EGM canreceive an indication from the remote server that the virtual ticketvoucher is valid for a particular value amount. In response, the EGM canredeem the virtual ticket voucher for an amount of credits equivalent tothe value amount. The EGM can notify the remote device that the virtualticket voucher has been redeemed and optionally notify the portableelectronic device. If the EGM receives an indication from the remoteserver that the virtual ticket voucher is no longer valid, then the EGMcan generate and output a notification message that indicates thevirtual ticket voucher is invalid. The notification message can includeone or more of 1) outputting a text message to a display on the EGM, 2)changing a state of a status indicator, such as a light array, 3)outputting a sound to an audio device on the EGM and 4) sending amessage for output on the portable electronic device.

In 314, the EGM can be configured to store virtual ticket voucherinformation. In one embodiment, the EGM can store a rendered image ofthe virtual ticket voucher. In another embodiment, the EGM can update amemory coupled to a cash box with the virtual ticket voucherinformation. In 316, hard and soft meters affected by the redemption ofthe virtual ticket voucher can be updated including soft meters foraccumulating a number of virtual ticket voucher accepted and a value ofthe virtual ticket vouchers accepted. In 318, the EGM can display theamount of credits or currency redeemed.

In 320, the EGM can generate a change voucher. If a value of the virtualticket voucher redeemed results in a fraction of credit based upon adenomination used on the EGM, such as 75 cents remaining on a dollardenomination machine, then the EGM can issue a change voucher. Thechange voucher is typically issued in a currency amount equivalent tosome fraction of a credit. In one embodiment, the EGM can issue aprinted ticket voucher for the change amount. In another embodiment theEGM can issue a virtual ticket voucher for the change amount. Details ofissuing virtual ticket vouchers are described as follows with respect toFIG. 5B as follows.

In 322, the EGM can enter into an operator mode. In one embodiment, theEGM can enter into an operator mode in response to an operator insertingan operator key. In 322, in operator mode, the EGM can be configured todisplay virtual ticket voucher information. For instance, the EGM can beconfigured to output values for soft meters associated with the virtualticket vouchers. In another example, the EGM can be configured todisplay virtual ticket voucher information associated with virtualticket vouchers accepted by the EGM. In one embodiment, the EGM can beconfigured to render images of the virtual ticket vouchers and/orprinted ticket vouchers received at the EGM. The rendered images can beused for dispute resolution purposes. In particular embodiment, the EGMcan be configured to receive portable device identification information,locate virtual ticket vouchers received from the portable electronic anddisplay the virtual ticket voucher information to a display on the EGMor to a display on a portable electronic device carried by the operator.

FIG. 5B is a method 400 in a gaming machine for issuing virtual ticketvouchers on a gaming machine. In 402, the EGM can detect an activationof an E-cash out button. In various embodiments, the E-cash out buttoncan be a mechanical button coupled to the player interface on the EGM, atouch screen button located on a display on the EGM or an input buttonon a portable electronic device in communication with the EGM, such as atouch screen button generated by an application executing on theportable electronic device. In response to detecting the activation ofthe E-cash out button, the EGM can initiate a countdown timer. Inaddition, in one embodiment, the EGM can be configured to activate awireless interface on the EGM and change a status indicator to indicatethe wireless interface is activated and ready to transmit virtual ticketvoucher information from the EGM. In another embodiment, the EGM canalready be in communication with the portable electronic device and theactivation of the wireless interface and changing a state of the statusindicator may not be necessary.

In 406, the EGM can request virtual ticket voucher information from theremote server. The request can include an amount for the virtual ticketvoucher. The virtual ticket voucher information can include a uniqueticket validation number and a ticket number. The ticket number canindicate that the ticket voucher is a virtual ticket voucher as opposedto a printed ticket voucher. In 408, the EGM can generate the virtualticket voucher. In 410, the EGM can transmit virtual ticket informationto the portable electronic device and receive information from theportable electronic device, such as device identification information.In one embodiment, if a near field communication interface is used, thetransmission can require a user to bring the portable electronic devicewithin a threshold distance of the interface for the transmission totake place. In 412, the EGM can send information received from theportable electronic device to the remote server, such as a portabledevice identification number. The device information can be associatedwith the virtual ticket voucher information stored on the remote device.In one embodiment, the device information can be used later in theredemption of the virtual ticket voucher. For instance, unless thecorrect device information associated with the virtual ticket voucher isreceived, the remote server won't validate the virtual ticket voucher.

In 414, the EGM can determine the countdown timer has expired and thevirtual ticket voucher transaction is not been completed. In response,in 416, the EGM can generate a printed ticket voucher with a valueamount the same as the virtual ticket voucher. The EGM may change theticket number to indicate that a printed ticket voucher is being issued.In addition, the EGM can also notify the remote server that the ticketvoucher was issued as printed ticket voucher and not a virtual ticketnumber. The remote server can change the ticket number associated withthe printed ticket voucher to reflect the ticket voucher is a printedticket voucher. In 418, the EGM can update various soft and/or hardmeters depending on the type of ticket voucher issued (virtual orprinted) and the value of the ticket voucher.

In 420, the EGM can enter an operator mode, such as for the purposes ofreading the soft meters or for dispute resolution. In 422, the EGM canbe configured to display virtual ticket voucher information associatedwith previously issued virtual ticket vouchers. In one embodiment, theEGM can be configured to display both virtual ticket information andprinted ticket voucher information for previously issued ticketvouchers. The information can include device information, such as uniquedevice identification information associated with a portable electronicdevice that received the virtual ticket voucher. In one embodiment,images of the virtual ticket vouchers that are formatted like a printedticket voucher can be rendered to the display.

Next additional details of EGMs and gaming systems are described withrespect to FIGS. 6 and 7. FIG. 6 shows a block diagram of a gamingsystem 600 in accordance with the described embodiments. The gamingsystem 600 can include one or more servers, such as server 602, and avariety of gaming devices including but not limited to table gamingdevices, such as 652, mobile gaming devices, such as 654, and slot-typegaming devices, such as 656. The table gaming devices, such as 652, caninclude apparatus associated with table games where a live operator or avirtual operator is employed. The gaming devices and one or more serverscan communicate with one another via a network 601. The network caninclude wired, wireless or a combination of wired and wirelesscommunication connections and associated communication routers.

Some gaming devices, such as 652, 654 and 656, can be configured with aplayer interface that allows at least 1) selections, such as a wageramount, associated with a wager-based game to be made and 2) an outcomeof the wager-based game to be displayed. As an example, gaming devices,652, 654 and 656, include player interfaces, 652 a, 654 a and 656 a,respectively. Typically, gaming devices with a player interface arelocated in publically accessible areas, such as a casino floor. On theother hand, some gaming devices, such as server 602, can be located inpublically inaccessible areas, such is in a back-room of a casino oreven off-site from the casino. Gaming devices located in publicallyinaccessible areas may not include a player interface. For instance,server 602 does not include a player interface. However, server 602includes an administrator interface 635 that allows functions associatedwith the server 602 to be adjusted.

An example configuration of a gaming device is described with respect togaming device 604. The gaming device 604 can include 1) a gamecontroller 606 for controlling a wager-based game played on the gamingdevice and 2) a player interface 608 for receiving inputs associatedwith the wager-based game and for displaying an outcome to thewager-based game. In more detail, the game controller 606 can include a)one or more processors, such as 626, b) memory for holding softwareexecuted by the one or more processors, such as 628, c) a power-hittolerant memory, such as 630, d) one or more trusted memories, such as632, e) a random number generator and f) a plurality of softwareapplications, 610. The other gaming devices, including table gamingdevice 652, mobile gaming device 654, slot-type gaming device 656 andserver 602, can each include a game controller with all or a portion ofthe components described with respect to game controller 606.

In particular embodiments, the gaming device can utilize a “state”machine architecture. In a “state” machine architecture criticalinformation in each state is identified and queued for storage to apersistent memory. The architecture doesn't advance to the next statefrom a current state until all the critical information that is queuedfor storage for the current state is stored to the persistent memory.Thus, if an error condition occurs between two states, such as a powerfailure, the gaming device implementing the state machine can likely berestored to its last state prior to the occurrence of the errorcondition using the critical information associated with its last statestored in the persistent memory. This feature is often called a “rollback” of the gaming device. Examples of critical information can includebut are not limited to an outcome determined for a wager-based game, awager amount made on the wager-based game, an award amount associatedwith the outcome, credits available on the gaming device and a depositof credits to the gaming device.

The power-hit tolerant memory 630 can be used as a persistent memory forcritical data, such as critical data associated with maintaining a“state” machine on the gaming device. One characteristic of a power-hittolerant memory 630 is a fast data transfer time. Thus, in the event ofa power-failure, which might be indicated by a sudden power fluctuation,the critical data can be quickly loaded from volatile memory, such asRAM associated with the processor 626, into the power-hit tolerantmemory 630 and saved.

In one embodiment, the gaming device 605 can be configured to detectpower fluctuations and in response, trigger a transfer of critical datafrom RAM to the power-hit tolerant memory 630. One example of apower-hit tolerant memory 630 is a battery-backed RAM. The batterysupplies power to the normally volatile RAM so that in the event of apower failure data is not lost. Thus, a battery-backed RAM is also oftenreferred to as a non-volatile RAM or NV-RAM. An advantage of abattery-backed RAM is that the fast data transfer times associated witha volatile RAM can be obtained.

The trusted memory 632 is typically a read-only memory of some type thatmay be designed to be unalterable. An EPROM or EEPROM are two types ofmemory that can be used as a trusted memory 632. The gaming device 604can include one or more trusted memories. Other types of memories, suchas Flash memory, can also be utilized as an unalterable memory and theexample of an EPROM or EEPROM is provided for purposes of illustrationonly.

Prior to installation the contents of a trusted memory, such as 632, canbe verified. For instance, a unique identifier, such as a hash value,can be generated on the contents of the memory and then compared to anaccepted hash value for the contents of the memory. The memory may notbe installed if the generated and accepted hash values do not match.After installation, the gaming device can be configured to check thecontents of the trusted memory. For instance, a unique identifier, suchas a hash value, can be generated on contents of the trusted memory andcompared to an expected value for the unique identifier. If thegenerated value of the unique identifier and the expected value of theunique identifier don't match, then an error condition can be generatedon the gaming device 604. In one embodiment, the error condition canresult in the gaming device entering a tilt state where game play istemporarily disabled on the gaming device.

Sometimes verification of software executed on the gaming device 604 canbe performed by a regulatory body, such as a government agency. Oftensoftware used by a game controller, such as 606, can be highlyregulated, where only software approved by a regulatory body is allowedto be executed by the game controller 606. In one embodiment, thetrusted memory 632 can store authentication programs and/orauthentication data for authenticating the contents of various memorieson the gaming device 604. For instance, the trusted memory 632 can storean authentication program that can be used to verify the contents of amass storage device, such as 620, which can include software executed bythe game controller 606.

The random number generator (RNG) 634 can be used to generate randomnumbers that can be used to determine outcomes for a game of chanceplayed on the gaming device. For instance, for a mechanical or videoslot reel type of game, the RNG, in conjunction with a paytable thatlists the possible outcomes for a game of chance and the associatedawards for each outcome, can be used to generate random numbers fordetermining reel positions that display the randomly determined outcomesto the wager-based game. In other example, the RNG might be used torandomly select cards for a card game. Typically, as described above,the outcomes generated on a gaming device, such as 604, are consideredcritical data. Thus, generated outcomes can be stored to the power-hittolerant memory 630.

Not all gaming devices may be configured to generate their own gameoutcomes and thus, may not use an RNG for this purpose. In someembodiments, game outcomes can be generated on a remote device, such asserver 602, and then transmitted to the gaming device 604 where theoutcome and an associated award can be displayed to the player via theplayer interface 608. For instance, outcomes to a slot-type game or acard game can be generated on server 602 and transmitted to the gamingdevice 604.

In other embodiments, the gaming device 604 can be used to play centraldetermination games, such as bingo and lottery games. In a centraldetermination game, a pool of game outcomes can be generated and then,particular game outcomes can be selected as needed (e.g., in response toa player requesting to play the central determination game) from thepool of previously generated outcomes. For instance, a pool of gameoutcomes for a central determination game can be generated and stored onserver 602. Next, in response to a request to play the centraldetermination game on gaming device 604, one of the outcomes from thepool can be downloaded to the gaming device 604. A game presentationincluding the downloaded outcome can be displayed on the gaming device604.

In other embodiments, thin client type gaming devices, such as mobilegaming devices used to play wager-based video card or video slot games,may be configured to receive at least game outcomes from a remote deviceand not use an RNG to generate game outcomes locally. The game outcomescan be generated remotely in response to inputs made on the mobiledevice, such as an input indicating a wager amount and/or an input toinitiate the game. This information can be sent from the mobile deviceto a remote device, such as from mobile gaming device 654 to server 602.After receiving the game outcome from the remote device, a gamepresentation for the game outcomes generated remotely can be generatedand displayed on the mobile device. In some instances, the gamepresentation can also be generated remotely and then streamed fordisplay to the mobile device.

The game controller 606 can be configured to utilize and execute manydifferent types of software applications 610. Typically, the softwareapplications utilized by the game controller 606 can be highly regulatedand may undergo a lengthy approval process before a regulatory bodyallows the software applications to be utilized on a gaming devicedeployed in the field, such as in a casino. One type of softwareapplication the game controller can utilize is an Operating System (OS).The OS can allow various programs to be loaded for execution by theprocessor 626, such as programs for implementing a state machine on thegaming device 606. Further, the OS can be used to monitor resourceutilization on the gaming device 606. For instance, certainapplications, such as applications associated with game outcomegeneration and game presentation that are executed by the OS can begiven higher priority to resources, such as the processor 626 and memory628, than other applications that can be executing simultaneously on thegaming device.

As previously described, the gaming device 604 can execute software fordetermining the outcome of a wager-based game and generating apresentation of the determined game outcome including displaying anaward for the game. As part of the game outcome presentation one or moreof 1) electro-mechanical devices, such as reels or wheels, can beactuated, 2) video content can be output to video displays, 3) soundscan be output to audio devices, 4) haptic responses can be actuated onhaptic devices or 5) combinations thereof, can be generated undercontrol of the game controller 606. The peripheral devices used togenerate components of the game outcome presentation can be associatedwith the player interface 608 where the types of devices that areutilized for the player interface 608 can vary from device to device.

To play a game, various inputs can be required. For instance, via inputdevices coupled to the gaming device 604, a wager amount can bespecified, a game can be initiated or a selection of a game choiceassociated with the play of the game can be made. The software 610executed by the game controller 606 can be configured to interpretvarious signals from the input devices, such as signals received from atouch screen controller or input buttons, and affect the game played onthe gaming device in accordance with the received input signals. Theinput devices can also be part of the player interface 608 provided withthe gaming device, such as 604.

In other embodiments, the gaming software 610 executed by the gamecontroller 606 can include applications that allow a game historyincluding the results of a number of past games to be stored, such asthe previous 10 or 100 games played on the gaming device 604. The gamehistory can be stored to a persistent memory including but not limitedto the power-hit tolerant memory 630. The gaming controller 606 canconfigured to provide a menu (typically, only operator accessible), thatallows the results of a past game to be displayed via the playerinterface 608. The output from the history menu can include are-creation of the game presentation associated with a past gameoutcome, such as a video representation of card hand associated with avideo poker game, a video representation of a reel configurationassociated with a video slot game, and/or raw data associated with thepast game result, such as an award amount, an amount wagered, etc. Thehistory menu can be used for dispute resolution purposes, such as if aplayer complains that they have not been properly awarded for a gamepreviously played on the gaming device 604.

The reporting software can be used by the game controller 606 to reportevents that have occurred on the gaming device 604 to remote device,such as server 602. For instance, in one embodiment, the game controller606 can be configured to report error conditions that have been detectedon the gaming device 604, such as if a device has malfunctioned or needsattention. For instance, the reporting software can be used to send amessage from the gaming device 604 to the server 602 indicating that aprinter on the gaming device needs a refill of tickets. In anotherembodiment, the gaming controller 606 can be configured to reportsecurity events that may have occurred on the gaming device 604, such asbut not limited to if a door is opened, a latch is activated or aninterior portion of the gaming device 604 has been accessed.

In yet other embodiments, the game controller 606 can be configured toreport gaming activity and associated events that has been generated onthe gaming device, such as a deposit of cash or an indicia of credit, atthe gaming device, a generation of game outcome including an associatedaward amount and a dispensation of cash or an indicia of credit from thegaming device 604. As part of a loyalty program, the gaming activity canbe associated with a particular player. The reporting software caninclude player tracking elements that allow the gaming activity of aparticular player to be reported to a remote device, such as server 602.

The game controller 606 can execute the authentication software toverify the authenticity of data and/or software programs executed on thegaming device 604. For instance, the authentication software can be usedto verify the authenticity of data and/or software applications whenthey are first downloaded to the gaming device 604. Further, theauthentication software can be used to periodically verify theauthenticity of data and/or software applications currently residing onthe gaming device, such as software applications stored on one of thememories coupled to the gaming device 604 including applications loadedinto the memory 628 for execution by the processor 626.

The communication software executed by the game controller 606 can beused to communicate with a variety of devices remote to the gamingdevice 604. For instance, the communication software can be used tocommunicate with one or more of a) servers remote to the device, such as602, b) other gaming devices, such as table gaming device 652, mobilegaming device 654 and slot-type gaming device 656 and c) mobile devicescarried by casino personnel or players in the vicinity of the gamingdevice 604. Via the communication software, the game controller can beconfigured to communicate via many different communication protocols.For instance, different wireless and/or wired communication protocolscan be implemented. Further, proprietary or non-proprietary gamingspecific protocols can be implemented. For instance, gaming specificnon-proprietary communication protocols, such as G2S (game to system),GDS (gaming device standard) and S2S (system to system) communicationprotocols provided by the Gaming Standards Association (GSA), Fremont,Calif., can be implemented on the gaming devices described herein.

The gaming device 604 can communicate with one or more remote devicesvia one or more network interfaces, such as 612. For instance, vianetwork interfaces 612 and the network 601, the gaming device 604 cancommunicate with other gaming devices, such as server 602 and/or gamingdevices, 652, 654 and 656. The network interfaces can provide wired orwireless communications pathways for the gaming device 604. Some gamingdevices may not include a network interface or can be configured tooperate in a stand-alone mode where the network interface is notconnected to a network.

In other embodiments, a mobile device interface or interfaces, such as614, can be provided for communicating with a mobile device, such as acell phone or a tablet computer carried by players or casino personneltemporarily in the vicinity of the gaming device 604. A wirelesscommunication protocol, such as Bluetooth™ and a Wi-Fi compatiblestandard, can be used for communicating with the mobile devices via themobile device interfaces 614. In one embodiment, the mobile deviceinterface can implement a short range communication protocol, such as anear-field communication (NFC) protocol used for mobile walletapplications. NFC is typically used for communication distances of 4 cmor less. In addition, a wired communication interface, such as a dockingstation, can be integrated into the gaming device, such as 604. Thewired communication interface can be configured to providecommunications between the gaming device 604 and the mobile deviceand/or providing power to the mobile device.

Near field communication, or NFC, allows for simplified transactions,data exchange, and connections with a touch. Formed in 2004, the NearField Communication Forum (NFC Forum) promotes sharing, pairing, andtransactions between NFC devices and develops and certifies devicecompliance with NFC standards. NFC's short range helps keep encryptedidentity documents private. Thus, a smartphone or tablet with an NFCchip can make a credit card/debit card payment to a gaming device orserve as keycard or ID card for a loyalty program. Further, an NFCdevice can act a hotel room key. The user of an NFC device as a hotelroom keys and/or a player tracking card instrument may allow fast VIPcheck-in and reduce staffing requirements.

NFC devices can read NFC tags on a gaming device 604 to get moreinformation about the gaming device including an audio or videopresentation. For instance, a tap of an NFC enabled device to a gamingdevice can be used to instantly share a contact, photo, song,application, video, or website link. In another example, an NFC enableddevice can be used to transfer funds to the gaming device or enter theplayer in a multi-player tournament. As another example, an NFC enableddevice can be used to receive information from a gaming device that canbe used in a persistent gaming application or a social mediaapplication.

Further, NFC enabled signage can include NFC tags that allow a patron tolearn more information about the content advertised in the signage. TheNFC enabled signage can be part of a gaming system. For instance, a signadvertising a show available at the casino can be configured to transferinformation about the show, show times and ticketing information via anNFC tag. As another example, a sign showing jackpot information, such asprogressive jackpot information, can be used to transfer informationabout the jackpot, such as the last time the jackpot was won and whereit was won.

In one embodiment, an NFC interface on a gaming device can be used toset-up a higher speed communication between the gaming device andanother NFC enabled device such as smart phone. The higher speedcommunication rates can be used for expanded content sharing. Forinstance, a NFC and Bluetooth enabled gaming device can be tapped by anNFC and Bluetooth enabled smart phone for instant Bluetooth pairingbetween the devices. Instant Bluetooth pairing between a gaming deviceand an NFC enabled device, such as a smartphone, can save searching,waiting, and entering codes. In another example, a gaming device can beconfigured as an NFC enabled router, such as a router supporting a Wi-Ficommunication standard. Tapping an NFC enabled device to an NFC enabledand Wi-Fi enabled gaming device can be used to establish a Wi-Ficonnection between the two devices.

The gaming device 604 can include one or more each of value inputdevices 616 and value output device 618. The value input devices 616 canbe used to deposit cash or indicia of credit onto the gaming device. Thecash or indicia of credit can be used to make wagers on games played onthe gaming device 604. Examples of value input devices 616 include butare not limited to a magnetic-striped card or smart card reader, a billand/or ticket acceptor, a network interface for downloading credits froma remote source, a wireless communication interface for reading creditdata from nearby devices and a coin acceptor. A few examples of valueinput devices are shown in FIG. 7.

The value output devices can be used to dispense cash or indicia ofcredit from the gaming device 604. Typically, the indicia of credit canbe exchanged for cash. For instance, the indicia of credit can beexchanged at a cashier station or at a redemption station. Examples ofvalue output devices can include a network interface for transferringcredits into a remote account, a wireless communication interface thatcan be used with a mobile device implementing mobile wallet application,a coin hopper for dispensing coins or tokens, a bill dispenser, a cardwriter, a printer for printing tickets or cards redeemable for cash orcredits. Another type of value output device is a merchandise dispenser,which can be configured to dispense merchandise with a tangible valuefrom a gaming device. A few examples of value output devices are shownin FIG. 7.

The combination of value input devices 616 and value output devices 618can vary from device to device. In some embodiments, a gaming device 604may not include a value input device or a value output device. Forinstance, a thin-client gaming device used in a mobile gamingapplication may not include a value input device and a value outputdevice. Instead, a remote account can be used to maintain the creditswon or lost from playing wager-based games via the mobile device. Themobile device can be used to access the account and affect the accountbalance via game play initiated on the mobile device. Credits can bedeposited or withdrawn from the remote account via some mechanism otherthan via the mobile device interface.

In yet other embodiments, the gaming device 604 can include one or moresecondary controllers 619. The secondary controllers can be associatedwith various peripheral devices coupled to the gaming device, such asthe value input devices and value output devices described in thepreceding paragraphs. As another example, the secondary controllers canbe associated with peripheral devices associated with the playerinterface 608, such as input devices, video displays, electro-mechanicaldisplays and a player tracking unit. In some embodiments, the secondarycontrollers can receives instructions and/or data from and provideresponses to the game controller 606. The secondary controller can beconfigured to interpret the instructions and/or data from the gamecontroller 606 and control a particular device according to the receivedinstructions and/or data. For instance, a print controller may receive aprint command with a number of parameters, such as a credit amount andin response print a ticket redeemable for the credit amount. In anotherexample, a touch screen controller can detect touch inputs and sendinformation to the game controller 606 characterizing the touch input.

In a particular embodiment, a secondary controller can be used tocontrol a number of peripheral devices independently of the gamecontroller 606. For instance, a player tracking unit can include one ormore of a video display, a touch screen, card reader, network interfaceor input buttons. A player tracking controller can control these devicesto provide player tracking services and bonusing on the gaming device604. In alternate embodiments, the game controller 604 can control thesedevices to perform player tracking functions. An advantage of performingplayer tracking functions via a secondary controller, such as a playertracking controller, is that since the player tracking functions don'tinvolve controlling the wager-based game, the software on the playertracking unit can be developed modified via a less lengthy andregulatory intensive process than is required for software executed bythe game controller 606, which does control the wager-based game. Ingeneral, using a secondary controller, certain functions of the gamingdevice 604 that are not subject to as much regulatory scrutiny as thegame play functions can be decoupled from the game controller 606 andimplemented on the secondary controller instead. An advantage of thisapproach, like for the player tracking controller, is that softwareapproval process for the software executed by the secondary controllercan be less intensive than the process needed to get software approvedfor the game controller.

A mass storage unit(s) 620, such as a device including a hard drive,optical disk drive, flash memory or some other memory storage technologycan be used to store applications and data used and/or generated by thegaming device 604. For instance, a mass storage unit, such as 620, canbe used to store gaming applications executed by the game controller 606where the gaming device 604 can be configured to receive downloads ofgame applications from remote devices, such as server 602. In oneembodiment, the game controller 606 can include its own dedicated massstorage unit. In another embodiment, critical data, such as game historydata stored in the power-hit tolerant memory 630 can be moved from thepower-hit tolerant memory 630 to the mass storage unit 620 at periodicintervals for archival purposes and to free up space in the power-hittolerant memory 630.

The gaming device 604 can include security circuitry 622, such assecurity sensors and circuitry for monitoring the sensors. The securitycircuitry 622 can be configured to operate while the gaming device isreceiving direct power and operational to provide game play as well aswhen the gaming device is uncoupled from direct power, such as duringshipping or in the event of a power failure. The gaming device 604 canbe equipped with one or more secure enclosures, which can include locksfor limiting access to the enclosures. One or more sensors can belocated within the secure enclosures or coupled to the locks. Thesensors can be configured to generate signals that can be used todetermine whether secure enclosures have been accessed, locks have beenactuated or the gaming device 604, such as a mobile device has beenmoved to an unauthorized area. The security monitoring circuitry can beconfigured to generate, store and/or transmit error events when thesecurity events, such as accessing the interior of the gaming device,have occurred. The error events may cause the game controller 606 toplace itself in a “safe” mode where no game play is allowed until theerror event is cleared.

The server 602 can be configured to provide one or more functions togaming devices or other servers in a gaming system 600. The server 602is shown performing a number of different functions. However, in variousembodiments, the functions can be divided among multiple servers whereeach server can communicate with a different combination of gamingdevices. For instance, player interface support 636 and gaming devicesoftware 638 can be provided on a first server, progressives can beprovided on a second server, loyalty program functions 640 andaccounting 648 can be provided on a third server, linked gaming 644 canbe provided on a fourth server, cashless functions 646 can be providedon a fifth server and security functions 650 can be provided on a sixthserver. In this example, each server can communicate with a differentcombination of gaming devices because each of the functions provided bythe servers may not be provided to every gaming device in the gamingsystem 600. For instance, the server 602 can be configured to provideprogressive gaming functions to gaming devices 604, 652 and 656 but notgaming device 654. Thus, the server 602 may not communicate with themobile gaming device 654 if progressive functions are not enabled on themobile gaming device at a particular time.

Typically, each server can include an administrator interface thatallows the functions of a server, such as 602, to be configured andmaintained. Each server 602 can include a processor and memory. In someembodiments, the servers, such as 602, can include a game controllerwith components, such as but not limited to a power-hit tolerant memory630, a trusted memory 632 and an RNG 634 described with respect togaming device 604. The servers can include one or more networkinterfaces on which wired or wireless communication protocols can beimplemented. Next, some possible functions provided by the server 602are described. These functions are described for the purposes ofillustration only and are not meant to be limiting.

The player interface support 636 can be used to serve content to gamingdevices, such as 604, 652, 654 and 656, remote to the server. Thecontent can include video and audio content that can be output on one ofthe player interfaces, such as 608, 652 a, 654 a and 656 a. Further, thecontent can be configured to utilize unique features of a particularplayer interface, such as video displays, wheels or reels, if theparticular player interface is so equipped.

In one embodiment, via the player interface support, content can beoutput to all or a portion of a primary video display that is used tooutput wager-based game outcomes on a player interface associated with agaming device. For instance, a portion of the primary display can beallocated to providing a “service window” on the primary video displaywhere the content in the service window is provided from a server remoteto the gaming device. In particular embodiments, the content deliveredfrom the server to a gaming device as part of the player interfacesupport 636 can be affected by inputs made on the gaming device. Forinstance, the service window can be generated on a touch screen displaywhere inputs received via the service window can be sent back to server602. In response, to the received inputs, the server 602 can adjust thecontent that is displayed on the remote gaming device that generated theinputs.

The “service window” application can be generated by software code thatis executed independently of other game controller software in a secure“sandbox.” Via the sandbox, an executable can be given limited access tovarious resources on an EGM, such as a portion of the CPU resources andmemory available on a game controller. The memory can be isolated fromthe memory used by other processes, such as game processes executed bythe game controller.

As described above, a service window application can be allowed tocontrol, send and/or receive data from secondary devices on a gamingdevice, such as a video display, a touch screen power interfaces orcommunication interfaces. A service window application allowed toutilize a communication interface, such as a wireless communicationinterface, can be configured to communicate with a portable electronicdevice via the communication interface. Thus, a service windowapplication can be configured to implement attract features as describedabove independently of a game controller on an EGM. Further details ofutilizing a service window on a gaming device on an EGM are described inU.S. patent application Ser. No. 12/209,608, by Weber et al., filed Sep.12, 2008, titled “Gaming Machine with Externally Controlled ContentDisplay,” which is incorporated herein by reference in its entirety andfor all purposes.

In another embodiment, via the video display, the service windowapplication can be configured to output data in an optical image format,such as a 1-D/2-D bar-code or a QR code. The optically formatted datacan be captured by a camera on the portable electronic device. Forinstance, a receipt indicating the acceptance of a virtual ticketvoucher or virtual currency on the gaming device can be displayed in theservice window in a QR code format and transferred to a user's portableelectronic device via an image capture device on their portableelectronic device. In another embodiment, virtual ticket voucherinformation can be transferred to a portable electronic device asoptically formatted image data.

If a player's identity is known, then the player interface support 636can be used to provide custom content to a remote gaming device, such as604. For instance, a player can provide identification information, suchas information indicating their membership in a loyalty program, duringtheir utilization of a gaming device. The custom content can be selectedto meet the identified player's interests. In one embodiment, theplayer's identity and interests can be managed via a loyalty program,such as via a loyalty program account associated with loyalty function640. The custom content can include notifications, advertising andspecific offers that are determined to be likely of interest to aparticular player.

The gaming device software function 638 can be used to provide downloadsof software for the game controller and/or second controllers associatedwith peripheral devices on a gaming device. For instance, the gamingdevice software 638 may allow an operator and/or a player to select anew game for play on a gaming device. In response to the game selection,the gaming device software function 638 can be used to download gamesoftware that allows a game controller to generate the selected game. Inanother example, in response to determining that a new counterfeit billis being accepted by bill acceptors in the gaming system 600, the gamingdevice software function 638 can be used to download a new detectionalgorithm to the bill acceptors that allow the counterfeit bill to bedetected.

The progressive gaming function 642 can be used to implement progressivegame play on one or more gaming devices. In progressive game play, aportion of wagers associated with the play of a progressive game isallocated to a progressive jackpot. A group of gaming devices can beconfigured to support play of the progressive game and contribute to theprogressive jackpot. In various embodiments, the gaming devicescontributing to a progressive jackpot may be a group of gaming devicescollocated near one another, such as a bank of gaming machines on acasino floor, a group of gaming devices distributed throughout a singlecasino, or group of gaming devices distributed throughout multiplecasinos (e.g., a wide area progressive). The progressive gaming function642 can be used to receive the jackpot contributions from each of thegaming devices participating in the progressive game, determine acurrent jackpot and notify participating gaming devices of the currentprogressive jackpot amount, which can be displayed on the participatinggaming devices if desired.

The loyalty function 640 can be used to implement a loyalty programwithin a casino enterprise. The loyalty function 640 can be used toreceive information regarding activities within a casino enterpriseincluding gaming and non-gaming activities and associate the activitieswith particular individuals. The particular individuals can be known ormay be anonymous. The loyalty function 640 can used to store a record ofthe activities associated with the particular individuals as well aspreferences of the individuals if known. Based upon the informationstored with the loyalty function 640 comps (e.g., free or discountedservices including game play), promotions and custom contents can beserved to the particular individuals.

The linked gaming function 644 can be used to used provide game playactivities involving player participating as a group via multiple gamingdevices. An example, a group of player might be competing against oneanother as part of a slot tournament. In another example, a group ofplayers might be working together in attempt to win a bonus that can beshared among the players.

The cashless function 646 can enable the redemption and the dispensationof cashless instruments on a gaming device. For instance, via thecashless function, printed tickets, serving as a cashless instrument,can be used to transfer credits from one gaming device to another gamingdevice. Further, the printed tickets can be redeemed for cash. Thecashless function can be used to generate identifying information thatcan be stored to a cashless instrument, such as a printed ticket, thatallows the instrument to later be authenticated. After authentication,the cashless instrument can be used for additional game play or redeemedfor cash.

The accounting function can receive transactional information fromvarious gaming devices within the gaming system 600. The transactionalinformation can relate to value deposited on each gaming device andvalue dispensed from each gaming device. The transactional information,which can be received in real-time, can be used to assess theperformance of each gaming device as well as an overall performance ofthe gaming system. Further, the transactional information can be usedfor tax and auditing purposes.

The security function 650 can be used to combat fraud and crime in acasino enterprise. The security function 650 can be configured toreceive notification of a security event that has occurred on a gamingdevice, such as an attempt at illegal access. Further, the securityfunction 650 can receive transactional data that can be used to identifyif gaming devices are being utilized in a fraudulent or unauthorizedmanner. The security function 650 can be configured to receive, storeand analyze data from multiple sources including detection apparatuslocated on a gaming device and detection apparatus, such as cameras,distributed throughout a casino. In response to detecting a securityevent, the security function 650 can be configured to notify casinopersonnel of the event. For instance, if a security event is detected ata gaming device, a security department can be notified. Depending on thesecurity event, one or more team members of the security department canbe dispatched to the vicinity of the gaming device. Next, a perspectivediagram of a slot-type gaming device that can include all or a portionof the components described with respect to gaming device 604 isdescribed.

FIG. 7 shows a perspective drawing of a gaming device 700 in accordancewith the described embodiments. The gaming device 700 is example of whatcan be considered a “thick-client.” Typically, a thick-client isconfigurable to communicate with one or more remote servers but providesgame play, such as game outcome determination, independent of the remoteservers. In addition, a thick-client can be considered as such becauseit includes cash handling capabilities, such as peripheral devices forreceiving cash, and a secure enclosure within the device for storing thereceived cash. In contrast, thin-client device, such as a mobile gamingdevice, may be more dependent on a remote server to provide a componentof the game play on the device, such as game outcome determination,and/or may not include peripheral devices for receiving cash and anassociated enclosure for storing it.

Many different configurations are possible between thick and thinclients. For instance, a thick-client device, such as 700, deployed in acentral determination configuration, may receive game outcomes from aremote server but still provide cash handling capabilities. Further, theperipheral devices can vary from gaming device to gaming device. Forinstance, the gaming device 700 can be configured withelectro-mechanical reels to display a game outcome instead of a videodisplay, such as 710. Thus, the features of gaming device 700 aredescribed for the purposes of illustration only and are not meant to belimiting.

The gaming device 700 can include a main cabinet 702. The main cabinet702 can provide a secure enclosure that prevents tampering with thedevice components, such as a game controller (not shown) located withinthe interior of the main cabinet and cash handing devices including acoin acceptor 720, a ticket printer 726 and a bill acceptor 718. Themain cabinet can include an access mechanism, such as door 704, whichallows an interior of the gaming device 700 to be accessed. Theactuation of the door 704 can be controlled by a locking mechanism, suchas lock 716. The lock 716, the door 704 and the interior of the maincabinet 702 can be monitored with security sensors for detecting whetherthe interior has been accessed. For instance, a light sensor can beprovided to detect a change in light-level in response to the door 704being opened.

The interior of the main cabinet 700 can include additional secureenclosure, which can also be fitted with locking mechanisms. Forinstance, the game controller, such as game controller 606, shown inFIG. 6, can be secured within a separate locked enclosure. The separatelocked enclosure for the game controller may allow maintenance functionsto be performed on the gaming device, such as emptying a drop box forcoins, emptying a cash box or replacing a device, while preventingtampering with the game controller. Further, in the case of device witha coin acceptor, 720, the separate enclosure can protect the electronicsof the game controller from potentially damaging coin dust.

A top box 706 can be mounted to the top of the main cabinet 702. Anumber of peripheral devices can be coupled to the top box 706. In FIG.7, a display device 708 and a candle device 714 are mounted to the topbox 706. The display device 708 can be used to display informationassociated with game play on the gaming device 700. For instance, thedisplay device 708 can be used to display a bonus game presentationassociated with the play of a wager-based game (One or more bonus gamesare often features of many wager-based games). In another example, thedisplay device 708 can be used to display information associated with aprogressive game, such as one or more progressive jackpot amounts. Inyet another example, the display device 708 can be used to display anattract feature that is intended to draw a potential player's attentionto the gaming device 700 when it is not in use.

The candle device 714 can include a number of lighting elements. Thelighting elements can be lit in different patterns to draw attention tothe gaming device. For instance, one lighting pattern may indicate thatservice is needed at the gaming device 700 while another light patternmay indicate that a player has requested a drink. The candle device 714is typically placed at the top of gaming device 700 to increase itsvisibility. Other peripheral devices, including custom bonus devices,such as reels or wheels, can be included in a top box 706 and theexample in FIG. 7 is provided for illustrative purposes only. Forinstance, some of the devices coupled to the main cabinet 702, such asprinter 726, can be located in a different top box configuration.

The gaming device 700 provides a player interface that allows the playof a game, such as wager-based game. In this embodiment, the playerinterface includes 1) a primary video display 710 for outputting videoimages associated with the game play, 2) audio devices, such as 722, foroutputting audio content associated with game play and possibly casinooperations, 3) an input panel 712 for at least providing game playrelated inputs and 4) a secondary video display 708 for outputting videocontent related to the game play (e.g., bonus material) and/or thecasino enterprise (e.g., advertising). In particular embodiments, one orboth of the video displays, 708 and 710, can be equipped with a touchscreen sensor and associated touch screen controller, for detectingtouch inputs, such as touch inputs associated with the play of a game ora service window output to the display device.

The input panel 712 can include a number of electro-mechanical inputbuttons, such as 730, and/or touch sensitive surfaces. For instance, theinput panel can include a touch screen equipped video display to providea touch sensitive surface. In some embodiments, the functions of theelectro-mechanical input buttons can be dynamically reconfigurable. Forinstance, the function of the electro-mechanical input buttons may bechanged depending on the game that is being played on the gaming device.To indicate function changes, the input buttons can each include aconfigurable display, such as an e-ink or a video display for indicatingthe function of button. The output of the configurable display can beadjusted to account for a change in the function of the button.

The gaming device 700 includes a card reader 728, a printer 726, a coinacceptor 720, a bill and/or ticket acceptor 720 and a coin hopper (notshown) for dispensing coins to a coin tray 732. These devices canprovide value input/output capabilities on the gaming device 700. Forinstance, the printer 726 can be used to print out tickets redeemablefor cash or additional game play. The tickets generated by printer 726as well as printers on other gaming devices can be inserted into billand ticket acceptor 718 to possibly add credits to the gaming device700. After the ticket is authenticated, credits associated with theticket can be transferred to the gaming device 700.

The device 718 can also be used to accept cash bills. After the cashbill is authenticated, it can be converted to credits on the gamingdevice and used for wager-based game play. The coin acceptor 720 can beconfigured to accept coins that are legal tender or tokens, such astokens issued by a casino enterprise. A coin hopper (not shown) can beused to dispense coins that are legal tender or tokens into the cointray 732.

The various aspects, embodiments, implementations or features of thedescribed embodiments can be used separately or in any combination.Various aspects of the described embodiments can be implemented bysoftware, hardware or a combination of hardware and software. Thecomputer readable medium is any data storage device that can store datawhich can thereafter be read by a computer system. Examples of thecomputer readable medium include read-only memory, random-access memory,CD-ROMs, DVDs, magnetic tape and optical data storage devices. Thecomputer readable medium can also be distributed over network-coupledcomputer systems so that the computer readable code is stored andexecuted in a distributed fashion.

The foregoing description, for purposes of explanation, used specificnomenclature to provide a thorough understanding of the invention.However, it will be apparent to one skilled in the art that the specificdetails are not required in order to practice the invention. Thus, theforegoing descriptions of specific embodiments of the present inventionare presented for purposes of illustration and description. They are notintended to be exhaustive or to limit the invention to the precise formsdisclosed. It will be apparent to one of ordinary skill in the art thatmany modifications and variations are possible in view of the aboveteachings.

The embodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious embodiments with various modifications as are suited to theparticular use contemplated. It is intended that the scope of theinvention be defined by the following claims and their equivalents.

While the embodiments have been described in terms of several particularembodiments, there are alterations, permutations, and equivalents, whichfall within the scope of these general concepts. It should also be notedthat there are many alternative ways of implementing the methods andapparatuses of the present embodiments. It is therefore intended thatthe following appended claims be interpreted as including all suchalterations, permutations, and equivalents as fall within the truespirit and scope of the described embodiments.

What is claimed is:
 1. An electronic gaming machine (EGM) comprising: acabinet; a display mounted to the cabinet; a wireless interface forcommunicating with a portable electronic device; a network interface forcommunicating with a validation server secured within the cabinet; aprinter configured to print ticket vouchers communicatively coupled to agame controller secured within the cabinet; a cash out button coupled tothe game controller for generating a signal to transfer value from theEGM via a printed ticket voucher; the game controller including aprocessor and a memory secured within the cabinet configured to 1)control a wager-based game played on the electronic gaming machine; 2)issue virtual ticket voucher and printed ticket vouchers; 3) receive anindication, separate from the cash out button signal, to transfer valuefrom the EGM via a virtual ticket voucher, receive a validation numberfrom the validation server via the network interface, generate thevirtual ticket voucher including the validation number, and issue thevirtual ticket voucher by transmitting the virtual ticket voucher to theportable electronic device via the wireless interface; and 4) cancel thegenerated virtual ticket voucher based on a determination that thegenerated virtual ticket voucher was not transferred to the portableelectronic device within a predetermined amount of time and issue aprinted ticket voucher instead of the canceled virtual ticket voucher byinstructing the printer to generate the printed ticket voucher, theprinted ticket voucher including the validation number of the canceledvirtual ticket voucher.
 2. The EGM of claim 1, wherein the gamecontroller is further configured to send a message to the validationserver indicating the virtual ticket voucher is issued.
 3. The EGM ofclaim 1, wherein the game controller is further configured to send amessage to the validation server indicating that the printed voucher isissued instead of the virtual ticket voucher.
 4. The EGM of claim 1,wherein the game controller is further configured to update one or morehard meters in response to issuing the virtual ticket voucher.
 5. TheEGM of claim 1, wherein the game controller is further configured, inresponse to issuing the virtual ticket voucher to update a first softmeter that accumulates a number of virtual tickets issued and a secondsoft meter that accumulates a value of the virtual tickets issued. 6.The EGM of claim 5, wherein game controller is further configured toenter into an operator mode and output a value associated with the firstsoft meter and a value associated with the second soft meter.
 7. The EGMof claim 1, wherein the game controller is further configured to includea ticket voucher number with the generated virtual ticket voucherwherein a portion of the ticket voucher number is formatted todifferentiate between the virtual ticket voucher and the printed ticketvoucher.
 8. The EGM of claim 1, wherein the game controller is furtherconfigured to receive a second validation number from the validationserver for the printed ticket voucher.
 9. The EGM of claim 1, whereinthe game controller is further configured to render a front side imageand/or a back side images of the virtual ticket voucher to the display.10. The EGM of claim 9, wherein front side images and/or back sideimages of the virtual ticket voucher are formatted to appear similar tothe printed ticket voucher.
 11. The EGM of claim 9, wherein the gamecontroller is further configured to store the rendered front side imageand/or back side images.
 12. The EGM of claim 1, wherein the gamecontroller is further configured to enter into a dispute resolution modeand in response display information associated with the virtual ticketvoucher issued.
 13. The EGM of claim 1, wherein the game controller isfurther configured to receive unique portable device identificationinformation from the portable electronic device to which the virtualvoucher is issued.
 14. The EGM of claim 13, wherein the game controlleris further configured to store the unique portable device identificationinformation with a record of the virtual ticket voucher issued.
 15. TheEGM of claim 14, wherein the game controller is further configured toenter into a dispute resolution mode, receive the unique portable deviceidentification information and locate the record of the virtual ticketvoucher issued using the unique portable device identificationinformation.
 16. The EGM of claim 13, wherein the game controller isfurther configured to send the unique portable device information to thevalidation server.
 17. The EGM of claim 1, further comprising a secondbutton coupled to the game controller for generating a signal totransfer value from the EGM via a virtual ticket voucher wherein thesignal provides the indication to the EGM.
 18. The EGM of claim 1,wherein the game controller is further configured to receive theindication to transfer value from the EGM via the virtual ticket voucherfrom the portable electronic device.
 19. The EGM of claim 18, whereinthe game controller is further configured to generate an image of thevirtual ticket voucher and output the image to the display prior totransferring the virtual ticket voucher to the portable electronicdevice.
 20. The EGM of claim 1, wherein the wireless interface is a nearfield communication protocol compatible interface.
 21. The EGM of claim1, wherein a range of the wireless interface is less than 4 CM.
 22. TheEGM of claim 1, further comprising: a status indicator including one ormore lighting elements wherein the game controller is configured tochange a state of the status indicator to indicate that the EGM is readyto transmit the virtual ticket voucher to the portable electronicdevice.
 23. The EGM of claim 1, wherein the game controller is furtherconfigured to receive second virtual ticket voucher informationincluding a second ticket validation number from the portable electronicdevice via the wireless interface, validate the second virtual ticketvoucher with the validation server and deposit a value amount associatedwith the second virtual ticket voucher to the EGM.